You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: