BuddyNS delegation lab
Zoom in/out with your mouse wheel or trackpad.
Color | Indication | Color | Indication | Color | Indication |
---|---|---|---|---|---|
Zone. | Nameserver serving outdated data. | Nameserver from the BuddyNS backbone. | |||
Nameserver delegated by zone. | Server was queried and timed out. | Inconsistency between zone and registry. |
Geographical distribution of the Authority servers
Location | Server |
---|
Geographical locations are established via MaxMind's GeoLite technology. Some locations may be inexact.
Resolution completed
The DNS resolution trace from root DNS servers down to your authority completed successfully. Each server on the chain answered as expected.
See below for a detailed diagnostic of the delegation chain.
Delegation tests for zone
Test | Result | Notes |
---|---|---|
Is Zone | OK | The indicated domain zone is a zone:
authority and nameserver data is announced for
it.
These are the authority parameters for zone zone :
|
Zone/Registry consistent | OK | The list of nameservers declared by the last delegating server and the authoritative server match. Configuration looks healthy. |
Authoritative servers consistent | OK | Every nameserver authoritative for zone
correctly serves the same zone version, so client queries
will get the same response regardless of the server
they reach. Here's the summary:
|
Number of servers | OK | zone delegates its DNS
to 6 servers. This is a sufficient
number to provide DNS continuity. RFC 2182 recommends 3 to 5
servers "when higher reliability is required": BuddyNS
recommends 4 or 5. |
Unresponsive nameservers | OK | All queried nameservers responded; no dead/misconfigured/unavailable server was found in the chosen resolution path. |
Recursion | OK | None of the DNS servers listed as
authoritative for zone serves recursive
queries to the public.
|
Truncation | OK | None of the DNS servers listed as
authoritative for zone gives a truncated
response for NS requests. Clients can successfully
perform NS queries over the low-latency UDP protocol,
without falling back to much slower TCP. |
IPv6 | OK | The authority declares one or more
servers as reachable via IPv6. IPv6-enabled clients can
resolve domains of zone natively, without
falling back to the compatibility IPv4 protocol.IPv6 score: 100% Here is the list of IPv6-enabled servers declared byzone :
|
DNSCurve | No | DNScurve is not supported for this zone. To leverage DNSCurve from BuddyNS, delegate zone using secure server names from BuddyNS. |
Delegation trace for zone
The delegation trace below is one of the possible traversals of the delegation tree. Note that:
- For zones with correct delegation, the same data is obtained regardless of which resolution path is traversed.
- BuddyNS excludes its own servers from traversals when foreign servers are available.
- Refresh this page to test with a different traversal path.
Here's the steps BuddyNS took to collect the DNS delegation chain for zone:
-
→ BuddyNS asks server f.root-servers.net.: "Which servers can answer to me about
zone
?"← Server f.root-servers.net. replied: "I can't tell you myself, but ask any one of the following guys:"
- v0n0.nic.zone
- v0n1.nic.zone
- v0n2.nic.zone
- v0n3.nic.zone
- v2n0.nic.zone
- v2n1.nic.zone
-
👍🏻 Found it! Server
v0n1.nic.zone
is authoritative for zonezone
!← It declares the following nameservers as authorities for
zone
:- v2n1.nic.zone
- v0n3.nic.zone
- v0n2.nic.zone
- v2n0.nic.zone
- v0n0.nic.zone
- v0n1.nic.zone