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
Using the test zones specified in zonemaster/zonemaster#1213 we have some test zones (scenarios) where NO_RESPONSE. For some of the test zones (scenarios) the tag is outputted, for others it is not. E.g. for test zone no-response.consistency06.xa none of the name server IP addresses are responding (on purpose) but the tag is not outputted.
After some investigation I have come to the following conclusion:
For a non-responding name server to be listed in NO_RESPONSE at lease one of the following requirements must be fullfilled:
The zone must be available and the name serverin question must be listed in that zone as an NS.
The name server in question must be included in the call as "fake delegation".
In case of no-response.consistency06.xa, the zone is not available since none of the name servers for it responds. By inspecting output from tcpdump I can see that queries are sent to the non-responding name server IPs.
First running the test of the zone using the delegated path from the private root:
Using the test zones specified in zonemaster/zonemaster#1213 we have some test zones (scenarios) where
NO_RESPONSE
. For some of the test zones (scenarios) the tag is outputted, for others it is not. E.g. for test zoneno-response.consistency06.xa
none of the name server IP addresses are responding (on purpose) but the tag is not outputted.After some investigation I have come to the following conclusion:
For a non-responding name server to be listed in
NO_RESPONSE
at lease one of the following requirements must be fullfilled:In case of
no-response.consistency06.xa
, the zone is not available since none of the name servers for it responds. By inspecting output from tcpdump I can see that queries are sent to the non-responding name server IPs.First running the test of the zone using the delegated path from the private root:
A second run with "fake delegation" added. Note that
NO_RESPONSE
now appear.The text was updated successfully, but these errors were encountered: