Trace a DNS delegation from the root to the final authoritative zone

Use a DNS trace when you need to see where delegation stops or leads to the wrong provider. A trace follows referrals from the root toward the authoritative zone, helping you distinguish a parent nameserver problem from a record inside the final zone.

01 Run a trace for the actual failing name

On a system with dig and permitted direct DNS access, substitute your hostname and required record type:

Command example
dig +trace www.example.com A

The result shows the servers used along the referral path. A name beneath com.ng or a delegated subdomain can involve additional levels. Read the server that supplied each response, not just the first nameserver name printed anywhere in the output.

02 Locate the first unexpected transition

  1. Confirm that the trace obtains the root referral and reaches the relevant top-level domain.
  2. Compare the parent referral for your domain with the nameservers you intended to publish.
  3. Check whether the referred servers answer authoritatively for the domain.
  4. If the hostname follows a CNAME or lies below another delegation, investigate the target or child zone as well.
  5. Save the trace with its time and run direct queries against the relevant authoritative servers to confirm the finding.

Why does a trace time out while ordinary browsing works?

A trace makes iterative queries from the machine running the command. A corporate network can allow access to its recursive resolver while blocking direct DNS to external servers. That does not prove that public authoritative DNS is broken. Test from an approved network that permits the required access or give the evidence to support.

Specifying @server with +trace affects the initial root-nameserver query; it does not make that server perform every step of the trace. Do not interpret the option as a test of one recursive resolver's entire cache.

Does a completed trace prove the website should load?

It confirms useful DNS path information, but it does not test the website server, HTTP response or certificate. A trace also displays DNSSEC-related records without establishing complete validation merely by printing them. Follow the result with targeted authoritative queries, validation checks where applicable and an application test.

  • 0 Users Found This Useful
  • domains-dns
Was this answer helpful?

Related Articles

Transfer an existing domain to Nabtech without overlooking DNS or eligibility

A domain transfer moves registrar management to us. It is separate from moving a website,...

Change nameservers for a domain registered with Nabtech

Change a domain registered with us's nameservers when you want a different DNS service to...

Create private nameservers and the matching DNS records

Private nameservers use your own domain, such as ns1.example.com and ns2.example.com. They need...

Understanding how your domain, DNS, website and email fit together

Your domain is the registered name people use, while hosting runs the website or email service...

Understand the DNS record types used for websites and business email

A DNS zone contains records that direct websites, email and other services. Choose the record...