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 greatfire.org
Test | Result | Notes |
---|---|---|
Is Zone | ERROR | The indicated domain is not a
zone: no authority information is
announced for it. may be a simple domain;
it is handled by parent zone greatfire.org.
No authoritative servers could be reached to fetch
authority parameters: this zone appears to be currently
blacked out of the Internet, no domains in it can be resolved.
|
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 | ERROR | Authoritative nameservers for greatfire.org are
serving inconsistent data. Clients may be confused by
getting different answers depending on what destination
nameserver they reached. The outdated zone data some
nameservers are publishing may reference records
pointing clients to IP addresses no longer in control
of greatfire.org's organization, thus incurring data
and identity theft. Serial numbers are:
|
Number of servers | ERROR | greatfire.org delegates its DNS
to 0 servers. This does not
fulfill DNS' requirements, which mandate a minimum of 2
servers for each zone. As soon as the server will experience
some downtime, all services associated with greatfire.org
will vanish from the Internet. You should get DNS redundancy
immediately to fix this, and most likely you can get this at
no cost with BuddyNS. |
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 greatfire.org serves recursive
queries to the public.
|
Truncation | OK | None of the DNS servers listed as
authoritative for greatfire.org 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 | WARNING | None of the servers serving
greatfire.org's DNS is reachable via IPv6.
IPv6-enabled clients greatfire.org will need
to revert to compatibility IPv4 protocol for every
look up of services of greatfire.org . A growing
number a IPv6-only clients will be unable to perform
such look ups.
IPv6 score: % |
DNSCurve | No | DNScurve is not supported for this zone. To leverage DNSCurve from BuddyNS, delegate greatfire.org using secure server names from BuddyNS. |
Delegation trace for greatfire.org
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 greatfire.org:
-
Ouch!
replies that
greatfire.org
does not exista zone.