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 qmail.jp
| Test | Result | Notes |
|---|---|---|
| Is Zone | ERROR | The indicated domain com.qmail.jp is not a
zone: no authority information is
announced for it. com.qmail.jp may be a simple domain;
it is handled by parent zone qmail.jp.
These are the authority parameters for zone qmail.jp:
|
| 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 qmail.jp
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 | ERROR | qmail.jp delegates its DNS
to 1 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 qmail.jp
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 qmail.jp serves recursive
queries to the public.
|
| Truncation | OK | None of the DNS servers listed as
authoritative for qmail.jp 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
qmail.jp's DNS is reachable via IPv6.
IPv6-enabled clients qmail.jp will need
to revert to compatibility IPv4 protocol for every
look up of services of qmail.jp. A growing
number a IPv6-only clients will be unable to perform
such look ups.
IPv6 score: 0% |
| DNSCurve | No | DNScurve is not supported for this zone. To leverage DNSCurve from BuddyNS, delegate qmail.jp using secure server names from BuddyNS. |
Delegation trace for qmail.jp
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 qmail.jp:
-
→ BuddyNS asks server k.root-servers.net.: "Which servers can answer to me about
qmail.jp?"← Server k.root-servers.net. replied: "I can't tell you myself, but ask any one of the following guys:"
- a.dns.jp
- b.dns.jp
- c.dns.jp
- d.dns.jp
- e.dns.jp
- f.dns.jp
- g.dns.jp
- h.dns.jp
-
→ BuddyNS asks server b.dns.jp: "Which servers can answer to me about
qmail.jp?"← Server b.dns.jp replied: "I can't tell you myself, but ask any one of the following guys:"
- b.ns.qmail.jp
- a.ns.qmail.jp
-
👍🏻 Found it! Server
a.ns.qmail.jpis authoritative for zoneqmail.jp!← It declares the following nameservers as authorities for
qmail.jp:- b.ns.qmail.jp