-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Engine fails to verify NS in zone #356
Comments
@vlevigneron, can you look at this issue? |
Is it OK with what we discussed earlier, I mean change status of |
Yes, it is. At least for now. I actually misread the message. Both are actually listed. Can you change from |
OK, I'll make a branch and new PR for that fix in the minutes. For the request to add a space. Yes I could do that, but, we have many cases of lists of item and there is never a space. I guess that if we want to change that, we should decide, then change all of them to be homogeneous. That's why I would not change that in this fix. |
I'll put this here again: #60 (but this is primarily for the JSON logs) |
Resolved by #357. |
NAMESERVER06 says that "All name servers names listed for a delegation must be resolvable in DNS", which I think should be interpreted as including all NS listed in the apex of the zone.
This issue shows that there is a problem with the tests of the NS in the zone. That must be corrected.
200.193.193.in-addr.arpa is delegated to ns.gu.kiev.ua and ns.lucky.net. We find the same to NS in the zone:
NS
ns.gu.kiev.ua
cannot be resolved to IP address:I would expect that Zonemaster sees that as an error, but it does not:
The text was updated successfully, but these errors were encountered: