[GH-ISSUE #196] management command "domains" checks only secondary dns #180

New issue

Closed

opened 2026-02-26 09:36:21 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @ThomasWaldmann on GitHub (Jan 12, 2015).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/196

the check that decides whether a domain is ok sends a query to the related DNS.

if there are 2 DNSs (namserver [primary] and nameserver2 [secondary]) configured in the DB, it prefers to send the query to the secondary. if the query fails, we should also check if querying the primary still works and only set the domain to unavailable if the primary failed also.

Originally created by @ThomasWaldmann on GitHub (Jan 12, 2015). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/196 the check that decides whether a domain is ok sends a query to the related DNS. if there are 2 DNSs (namserver [primary] and nameserver2 [secondary]) configured in the DB, it prefers to send the query to the secondary. if the query fails, we should also check if querying the primary still works and only set the domain to unavailable if the primary failed also.

kerem

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

closed this issue
added the
enhancement
label

kerem commented

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

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 26, 2015):

hmm, I read the resolver code and it looks like it will use all available nameservers anyway.
so the only choice we have is which to try first. i added a flag prefer_primary so we can check the primary ns first for the domain checker.

@ThomasWaldmann commented on GitHub (Jan 26, 2015): hmm, I read the resolver code and it looks like it will use all available nameservers anyway. so the only choice we have is which to try first. i added a flag prefer_primary so we can check the primary ns first for the domain checker.