Skip to content
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

Some nameservers are not resolved from Zonemaster, even though they were accessible #504

Closed
sandoche2k opened this issue Mar 13, 2019 · 4 comments
Assignees
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description
Milestone

Comments

@sandoche2k
Copy link
Contributor

https://zonemaster.net/result/b2fe4826d3fc1244

For the domain "myriam-kassem.fr", zonemaster had a nameserver warning saying that NS (ns200.anycast.me/46.105.207.200) for the domain was not accessible. But, when a dig request was made from the ZM VPS, for the same NS, it was resolving.

The issue was identified by @vlevigneron as an old code has been put in place to evict servers that were not responding.

@sandoche2k
Copy link
Contributor Author

Related to the BUG #438

@sandoche2k sandoche2k added this to the 2019.1 milestone Mar 13, 2019
@vlevigneron
Copy link
Contributor

Well, here is what I found out.
We have a blacklisting mechanism that prevents query multiple times servers that do not respond.
The servers ns200.anycast.me/dns200.anycast.me are blacklisted because they answer REFUSED to a '.' query. It's their right.
The issue is that we have the #438 BUG that does not make a difference between unreachable and REFUSED responses.

IMHO, we have 3 options :
1/ Fix #438. As the problem is perhaps in LDNS and not in zonemaster code, it is not easy to fix in a short term.
2/ Inhibits for the moment blacklisting mechanism. Very easy but could slower processing in case of really broken zones.
3/ Adapt blacklisting mechanism. Did some tests, not sure it will be very effective.

@sandoche2k sandoche2k added T-Bug Type: Bug in software or error in test case description P-High Priority: Issue to be solved before other labels Mar 13, 2019
@sandoche2k
Copy link
Contributor Author

@vlevigneron remove the blacklisting for now and close the issue. Also, create a new issue to put the blacklisting again.

@matsduf
Copy link
Contributor

matsduf commented Mar 19, 2019

Fixed by #511.

@matsduf matsduf closed this as completed Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description
Projects
None yet
Development

No branches or pull requests

4 participants