[GH-ISSUE #175] support secondary nameserver(s) #163

New issue

Closed

opened 2026-02-26 09:36:13 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @ThomasWaldmann on GitHub (Oct 31, 2014).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/175

we could also talk to a secondary ns instead of the primary one (the secondary is as uptodate as the primary).

that might help if the primary is overloaded / not reachable, but only works for queries, not for updates.

we could even prefer the secondary for queries.

Originally created by @ThomasWaldmann on GitHub (Oct 31, 2014). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/175 we could also talk to a secondary ns instead of the primary one (the secondary is as uptodate as the primary). that might help if the primary is overloaded / not reachable, but only works for queries, not for updates. we could even prefer the secondary for queries.

kerem

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

closed this issue
added the
enhancement
label

kerem commented

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

Author

Owner

@elnappo commented on GitHub (Oct 31, 2014):

do you mean a hidden primary dns server?

@elnappo commented on GitHub (Oct 31, 2014): do you mean a hidden primary dns server?

kerem commented

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

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 31, 2014):

well, for the service it is just the primary ns IP and secondary(ies) IP(s).
if one can reach the hidden primary to send updates to it, one can support that configuration.

@ThomasWaldmann commented on GitHub (Oct 31, 2014): well, for the service it is just the primary ns IP and secondary(ies) IP(s). if one can reach the hidden primary to send updates to it, one can support that configuration.