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

Already on GitHub? Sign in to your account

Depending on the local resolver has some consequences #3

Open
bortzmeyer opened this Issue Dec 27, 2012 · 1 comment

Comments

Projects
None yet
1 participant
Owner

bortzmeyer commented Dec 27, 2012

check-soa uses the local resolver to retrieve the list of NS.

For instance, if the local resolver validates with DNSSEC and the domain is broken (.MIL, today), the message is spurious:

% check-soa mil
No NS records for "mil.". It is probably a domain but not a zone

(The SERVFAIL in response to the NS query was misinterpreted)

@bortzmeyer bortzmeyer was assigned Dec 27, 2012

Owner

bortzmeyer commented Nov 22, 2014

The new option -ns solves partially the problem:

% check-soa -ns "$(dig +short +nodnssec @a.root-servers.net NS mil)" mil

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment