Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rdns settings not propagated if set using hcloud-cli #674

Closed
abbbi opened this issue Jan 16, 2024 · 1 comment
Closed

rdns settings not propagated if set using hcloud-cli #674

abbbi opened this issue Jan 16, 2024 · 1 comment
Labels

Comments

@abbbi
Copy link

abbbi commented Jan 16, 2024

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

@abbbi abbbi added the bug label Jan 16, 2024
@apricote
Copy link
Member

Worked for me in a quick test with the cli. We just do the same requests as frontend to the API.

Could you open a ticket with support so they can investigate what went wrong in the backend?

@jooola jooola closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants