[GH-ISSUE #302] related host: immediately create ns record #238

New issue

Open

opened 2026-02-26 09:36:51 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:36:51 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Mar 2, 2017).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/302

Currently, when adding a related host, the ns record won't be created immediately, but only after first dyndns update of the primary host (which can take a while when primary IP changes rarely).

There is a workaround via creating the update via the Web UI (host view, you can put arbitrary IPs there), but doing it automatically would be nice.

Originally created by @ThomasWaldmann on GitHub (Mar 2, 2017). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/302 Currently, when adding a related host, the ns record won't be created immediately, but only after first dyndns update of the primary host (which can take a while when primary IP changes rarely). There is a workaround via creating the update via the Web UI (host view, you can put arbitrary IPs there), but doing it automatically would be nice.

kerem added the

enhancement

label

2026-02-26 09:36:51 +03:00

kerem commented

2026-02-26 09:36:52 +03:00

Author

Owner

@gschintgen commented on GitHub (Jan 7, 2024):

I'm not even sure that the related hosts feature is working any longer at all for adding new hosts to an existing master.

I've just added a related host (on nsupdate.info) that I wanted to be IPv6-only, but after adding it the WebUI is showing the following for my new host:

IPv4 address: none      [expected result]
IPv4 interface ID: none [I left the field empty, so this is expected]
IPv6 Address: none      [UNEXPECTED!]
IPv6 interface ID: ::216......... [the configured ID]

I then tried updating ("nochg") the IPv6 of the master host. Nothing changed.
I added a few test hosts with an IPv4 Interface ID set to 0 (even though I don't want IPv4 for the actual host that I tried adding). Nothing.
I tried updating the IPv4 of the master. No change.
I unchecke the "Available" flag, updated, re-enabled, updated again. No success.

I can't get this to work.
BUT: All the (dual-stack) hosts that I previously configured for the very same master host show up just fine in the list of related hosts! Maybe there's something completely non-obvious that I'm missing and that I forgot since the last time I added a host, but seems doubtful to me.

@gschintgen commented on GitHub (Jan 7, 2024): I'm not even sure that the related hosts feature is working any longer *at all* for adding new hosts to an existing master. I've just added a related host (on nsupdate.info) that I wanted to be IPv6-only, but after adding it the WebUI is showing the following for my new host: ``` IPv4 address: none [expected result] IPv4 interface ID: none [I left the field empty, so this is expected] IPv6 Address: none [UNEXPECTED!] IPv6 interface ID: ::216......... [the configured ID] ``` I then tried updating ("nochg") the IPv6 of the master host. Nothing changed. I added a few test hosts with an IPv4 Interface ID set to 0 (even though I don't want IPv4 for the actual host that I tried adding). Nothing. I tried updating the IPv4 of the master. No change. I unchecke the "Available" flag, updated, re-enabled, updated again. No success. I can't get this to work. BUT: **All the (dual-stack) hosts that I previously configured for the very same master host show up just fine** in the list of related hosts! Maybe there's something completely non-obvious that I'm missing and that I forgot since the last time I added a host, but seems doubtful to me.

kerem commented

2026-02-26 09:36:52 +03:00

Author

Owner

@gschintgen commented on GitHub (Jan 7, 2024):

Oh well. The completely non-obvious step that I missed is that I had to do a fake update to a wrong address first! And then change back to the actual address. So it's not even about giving a nudge, but rather a shove to get the service to set related hosts up properly.
I really don't remember doing that for my previous hosts. Possibly even some regression?

@gschintgen commented on GitHub (Jan 7, 2024): Oh well. The completely non-obvious step that I missed is that I had to do a fake update to a wrong address first! And then change back to the actual address. So it's not even about giving a nudge, but rather a shove to get the service to set related hosts up properly. I really don't remember doing that for my previous hosts. Possibly even some regression?

kerem commented

2026-02-26 09:36:52 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 7, 2024):

Yes, that is because no-change updates sent to the service don't trigger dns zone updates (neither for main host nor for any related hosts).

So, the workaround is to update to a different IP and then update again to the desired IP (e.g. via the web interface).

@ThomasWaldmann commented on GitHub (Jan 7, 2024): Yes, that is because no-change updates sent to the service don't trigger dns zone updates (neither for main host nor for any related hosts). So, the workaround is to update to a *different* IP and then update again to the *desired* IP (e.g. via the web interface).

kerem referenced this issue

2026-02-26 10:31:26 +03:00

[PR #238] [MERGED] docs: add some info about DNSSEC, fixes #26 #423