You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hcloud server set-rdns server -r server.r.dns.host.name
which finished successfully. In the hetzner console it was to be seen that in the Network settings the RDNS hostname
was set, but attempting to reverse resolve the IP address still responded with the default RDNS entry.
I waited for another 12 hours and the settings were not propagated.
After resetting the RDNS Setting via hetzner console frontend and changing it again using the frtonend,
everything worked like expected.
Expected behavior
RDNS settings should be popagated if set via hcloud-cli
Observed behavior
RDNS settings were changed in the frontend but not applied
Minimal working example
No response
Log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
TL;DR
hi,
yesterday i attempted to set rdns settings via:
hcloud server set-rdns server -r server.r.dns.host.name
which finished successfully. In the hetzner console it was to be seen that in the Network settings the RDNS hostname
was set, but attempting to reverse resolve the IP address still responded with the default RDNS entry.
I waited for another 12 hours and the settings were not propagated.
After resetting the RDNS Setting via hetzner console frontend and changing it again using the frtonend,
everything worked like expected.
Expected behavior
RDNS settings should be popagated if set via hcloud-cli
Observed behavior
RDNS settings were changed in the frontend but not applied
Minimal working example
No response
Log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: