[GH-ISSUE #122] error: Base domain does not exist. (dns caching issue with the system resolver?) #117

New issue

Closed

opened 2026-02-26 09:35:47 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:35:47 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Dec 27, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/122

while we avoided caching issues at most places in the code (by just asking the authoritative master nameserver), there likely is one left which might byte you:

dnstools.parse_name with origin=None calls the normal system resolver, so caching effects might occur and that might lead to wrong computation of the zone we need to update in case the dns cache says your dynamic subzone does not exist (even if it does, because you created it a little later).

e.g. example.org exists, dyn.example.org does not yet exist.
you play around with nsupdate.info and trigger some lookup so dyn.example.org's non-existance is cached.

then you configure dyn.example.org so it exists, but nsupdate.info still says domain does not exist because of the caching.

not sure if we can do better, has to be investigated, code is a little twisted there.

Originally created by @ThomasWaldmann on GitHub (Dec 27, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/122 while we avoided caching issues at most places in the code (by just asking the authoritative master nameserver), there likely is one left which might byte you: dnstools.parse_name with origin=None calls the normal system resolver, so caching effects might occur and that might lead to wrong computation of the zone we need to update in case the dns cache says your dynamic subzone does not exist (even if it does, because you created it a little later). e.g. example.org exists, dyn.example.org does not yet exist. you play around with nsupdate.info and trigger some lookup so dyn.example.org's non-existance is cached. then you configure dyn.example.org so it exists, but nsupdate.info still says domain does not exist because of the caching. not sure if we can do better, has to be investigated, code is a little twisted there.

kerem

2026-02-26 09:35:47 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 09:35:47 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Dec 27, 2013):

query_ns --> get_ns_info --> parse_name --> system-resolver

think this is an api issue:

the whole api currently works based on passing around a fqdn and then determining via parse_name what's the host part and what's the origin zone.

if the api would pass around hostname and origin zone, we would not need to do that and could avoid using the system resolver as we could easily find out the correct master server to ask.

@ThomasWaldmann commented on GitHub (Dec 27, 2013): query_ns --> get_ns_info --> parse_name --> system-resolver think this is an api issue: the whole api currently works based on passing around a fqdn and then determining via parse_name what's the host part and what's the origin zone. if the api would pass around hostname and origin zone, we would not need to do that and could avoid using the system resolver as we could easily find out the correct master server to ask.

kerem commented

2026-02-26 09:35:47 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Jan 21, 2014):

could be also related to #138

@ThomasWaldmann commented on GitHub (Jan 21, 2014): could be also related to #138

kerem commented

2026-02-26 09:35:47 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Aug 30, 2014):