DNS Traversal
Trace DNS resolution from root servers through TLD to authoritative nameservers.
Authoritative Servers
Authoritative Servers
Authoritative nameservers are the final source of truth for a domain's DNS records. They hold the actual zone file and provide definitive answers rather than cached or referred data.
What You'll See
- The nameservers listed in your domain's NS records
- Direct DNS query responses with actual record values
- Response consistency between multiple authoritative servers
Diagnostic Value
- Verify all authoritative servers return consistent records
- Identify servers that are unreachable or misconfigured
- Detect zone transfer or synchronization issues between primary and secondary nameservers
History
The concept of authoritative nameservers was established in RFC 1034 (1987). Every domain must have at least two authoritative nameservers for redundancy, typically operated by the domain's DNS provider or hosting company.
Authoritative Servers
Authoritative nameservers are the final source of truth for a domain's DNS records. They hold the actual zone file and provide definitive answers rather than cached or referred data.
What You'll See
- The nameservers listed in your domain's NS records
- Direct DNS query responses with actual record values
- Response consistency between multiple authoritative servers
Diagnostic Value
- Verify all authoritative servers return consistent records
- Identify servers that are unreachable or misconfigured
- Detect zone transfer or synchronization issues between primary and secondary nameservers
History
The concept of authoritative nameservers was established in RFC 1034 (1987). Every domain must have at least two authoritative nameservers for redundancy, typically operated by the domain's DNS provider or hosting company.
Direct responses from the domain's authoritative nameservers.
ns3.cloudflare.com (162.159.0.33)
104.16.133.229, 104.16.132.229
ns5.cloudflare.com (162.159.2.9)
104.16.132.229, 104.16.133.229
ns4.cloudflare.com (162.159.1.33)
104.16.132.229, 104.16.133.229
ns6.cloudflare.com (162.159.5.6)
104.16.133.229, 104.16.132.229
ns7.cloudflare.com (162.159.4.8)
104.16.133.229, 104.16.132.229
TLD Servers
TLD Servers
Top-Level Domain (TLD) servers manage the registry for domain extensions like .com, .org, .net, and country codes like .uk or .de. They don't hold your actual DNS records but know which nameservers are authoritative for each domain.
What You'll See
- NS records pointing to your domain's authoritative nameservers
- Delegation information from the TLD registry
- Glue records (A records for nameservers in the same zone)
Diagnostic Value
- Verify your domain's delegation is correctly registered with the TLD
- Identify mismatches between registered nameservers and actual authoritative servers
- Detect broken or outdated delegation that prevents resolution
History
TLD servers emerged as the internet grew beyond a single authority. ICANN manages the root zone and delegates TLDs to registries. Verisign operates .com and .net (since 1991), while country-code TLDs are managed by national organizations.
TLD Servers
Top-Level Domain (TLD) servers manage the registry for domain extensions like .com, .org, .net, and country codes like .uk or .de. They don't hold your actual DNS records but know which nameservers are authoritative for each domain.
What You'll See
- NS records pointing to your domain's authoritative nameservers
- Delegation information from the TLD registry
- Glue records (A records for nameservers in the same zone)
Diagnostic Value
- Verify your domain's delegation is correctly registered with the TLD
- Identify mismatches between registered nameservers and actual authoritative servers
- Detect broken or outdated delegation that prevents resolution
History
TLD servers emerged as the internet grew beyond a single authority. ICANN manages the root zone and delegates TLDs to registries. Verisign operates .com and .net (since 1991), while country-code TLDs are managed by national organizations.
Delegation info from top-level domain servers.
l.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
j.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
h.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
d.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
b.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
f.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
k.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
m.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
i.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
g.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
a.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
c.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
e.gtld-servers.net: ns3.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
Root Servers
Root Servers
The 13 DNS root server clusters (A through M) form the foundation of the internet's DNS hierarchy. They don't know about individual domains but direct queries to the appropriate TLD servers.
What You'll See
- Referrals to TLD nameservers (e.g., .com servers for example.com)
- NS records for the top-level domain
- Response times from globally distributed root server anycast networks
Diagnostic Value
- Verify root servers can reach your TLD's nameservers
- Identify issues at the highest level of DNS hierarchy
- Confirm TLD delegation is properly configured in the root zone
History
The root server system began in 1983 with the original DNS implementation. The 13 root server identities (named A-M) were established by 1997. Today, each 'server' is actually a global anycast network - there are over 1,500 physical root server instances worldwide operated by 12 organizations including Verisign, ICANN, NASA, and various universities.
Root Servers
The 13 DNS root server clusters (A through M) form the foundation of the internet's DNS hierarchy. They don't know about individual domains but direct queries to the appropriate TLD servers.
What You'll See
- Referrals to TLD nameservers (e.g., .com servers for example.com)
- NS records for the top-level domain
- Response times from globally distributed root server anycast networks
Diagnostic Value
- Verify root servers can reach your TLD's nameservers
- Identify issues at the highest level of DNS hierarchy
- Confirm TLD delegation is properly configured in the root zone
History
The root server system began in 1983 with the original DNS implementation. The 13 root server identities (named A-M) were established by 1997. Today, each 'server' is actually a global anycast network - there are over 1,500 physical root server instances worldwide operated by 12 organizations including Verisign, ICANN, NASA, and various universities.
Delegation info from DNS root servers.
l.root-servers.net: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
j.root-servers.net: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
f.root-servers.net: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
h.root-servers.net: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
d.root-servers.net: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
b.root-servers.net: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
k.root-servers.net: k.gtld-servers.net, a.gtld-servers.net, i.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net, g.gtld-servers.net, f.gtld-servers.net, d.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, c.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net
i.root-servers.net: c.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net, d.gtld-servers.net, m.gtld-servers.net, f.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, l.gtld-servers.net
m.root-servers.net: d.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net, m.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net, l.gtld-servers.net, k.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net, j.gtld-servers.net, g.gtld-servers.net
e.root-servers.net: c.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net, d.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, g.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net
g.root-servers.net: c.gtld-servers.net, b.gtld-servers.net, g.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, a.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
c.root-servers.net: d.gtld-servers.net, k.gtld-servers.net, e.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net, f.gtld-servers.net, l.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net, m.gtld-servers.net, i.gtld-servers.net
a.root-servers.net: l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net, e.gtld-servers.net
Authoritative servers Response from ns3.cloudflare.com (162.159.0.33): 104.16.133.229 104.16.132.229 Response from ns5.cloudflare.com (162.159.2.9): 104.16.132.229 104.16.133.229 Response from ns4.cloudflare.com (162.159.1.33): 104.16.132.229 104.16.133.229 Response from ns6.cloudflare.com (162.159.5.6): 104.16.133.229 104.16.132.229 Response from ns7.cloudflare.com (162.159.4.8): 104.16.133.229 104.16.132.229 --- Top level domain servers Response from l.gtld-servers.net (192.41.162.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from j.gtld-servers.net (192.48.79.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from h.gtld-servers.net (192.54.112.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from d.gtld-servers.net (192.31.80.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from b.gtld-servers.net (192.33.14.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from f.gtld-servers.net (192.35.51.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from k.gtld-servers.net (192.52.178.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from m.gtld-servers.net (192.55.83.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from i.gtld-servers.net (192.43.172.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from g.gtld-servers.net (192.42.93.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from a.gtld-servers.net (192.5.6.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from c.gtld-servers.net (192.26.92.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com Response from e.gtld-servers.net (192.12.94.30): ns3.cloudflare.com ns5.cloudflare.com ns4.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com --- Root servers Response from l.root-servers.net (199.7.83.42): a.gtld-servers.net b.gtld-servers.net c.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net g.gtld-servers.net h.gtld-servers.net i.gtld-servers.net j.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net Response from j.root-servers.net (192.58.128.30): a.gtld-servers.net b.gtld-servers.net c.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net g.gtld-servers.net h.gtld-servers.net i.gtld-servers.net j.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net Response from f.root-servers.net (192.5.5.241): a.gtld-servers.net b.gtld-servers.net c.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net g.gtld-servers.net h.gtld-servers.net i.gtld-servers.net j.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net Response from h.root-servers.net (198.97.190.53): a.gtld-servers.net b.gtld-servers.net c.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net g.gtld-servers.net h.gtld-servers.net i.gtld-servers.net j.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net Response from d.root-servers.net (199.7.91.13): a.gtld-servers.net b.gtld-servers.net c.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net g.gtld-servers.net h.gtld-servers.net i.gtld-servers.net j.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net Response from b.root-servers.net (170.247.170.2): a.gtld-servers.net b.gtld-servers.net c.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net g.gtld-servers.net h.gtld-servers.net i.gtld-servers.net j.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net Response from k.root-servers.net (193.0.14.129): k.gtld-servers.net a.gtld-servers.net i.gtld-servers.net e.gtld-servers.net b.gtld-servers.net g.gtld-servers.net f.gtld-servers.net d.gtld-servers.net j.gtld-servers.net h.gtld-servers.net c.gtld-servers.net m.gtld-servers.net l.gtld-servers.net Response from i.root-servers.net (192.36.148.17): c.gtld-servers.net e.gtld-servers.net b.gtld-servers.net k.gtld-servers.net d.gtld-servers.net m.gtld-servers.net f.gtld-servers.net a.gtld-servers.net h.gtld-servers.net g.gtld-servers.net i.gtld-servers.net j.gtld-servers.net l.gtld-servers.net Response from m.root-servers.net (202.12.27.33): d.gtld-servers.net e.gtld-servers.net i.gtld-servers.net m.gtld-servers.net h.gtld-servers.net a.gtld-servers.net l.gtld-servers.net k.gtld-servers.net f.gtld-servers.net c.gtld-servers.net b.gtld-servers.net j.gtld-servers.net g.gtld-servers.net Response from e.root-servers.net (192.203.230.10): c.gtld-servers.net h.gtld-servers.net f.gtld-servers.net b.gtld-servers.net k.gtld-servers.net d.gtld-servers.net m.gtld-servers.net a.gtld-servers.net g.gtld-servers.net l.gtld-servers.net e.gtld-servers.net j.gtld-servers.net i.gtld-servers.net Response from g.root-servers.net (192.112.36.4): c.gtld-servers.net b.gtld-servers.net g.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net j.gtld-servers.net h.gtld-servers.net i.gtld-servers.net a.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net Response from c.root-servers.net (192.33.4.12): d.gtld-servers.net k.gtld-servers.net e.gtld-servers.net g.gtld-servers.net h.gtld-servers.net b.gtld-servers.net a.gtld-servers.net f.gtld-servers.net l.gtld-servers.net c.gtld-servers.net j.gtld-servers.net m.gtld-servers.net i.gtld-servers.net Response from a.root-servers.net (198.41.0.4): l.gtld-servers.net j.gtld-servers.net h.gtld-servers.net d.gtld-servers.net b.gtld-servers.net f.gtld-servers.net k.gtld-servers.net m.gtld-servers.net i.gtld-servers.net g.gtld-servers.net a.gtld-servers.net c.gtld-servers.net e.gtld-servers.net