Skip to main content
Track DNS is a small wrapper around the standard DNS lookup utilities. Two tools on one page: a record lookup (like nslookup) and a route trace (like a poor man’s dig +trace).
Track DNS page with Domain Lookup and Trace tabs

​
Domain Lookup

Type a hostname, hit lookup, see the records. The query runs from the cPanel server (not from your browser), so it shows what the server sees. Useful for:
  • “Did my A record actually update?” Type your domain, see the IP.
  • “Are my MX records pointing where I think?” Switch the record type to MX.
  • “Why is mail rejecting?” Look up SPF (TXT), DKIM (TXT at selector._domainkey.domain.com), DMARC (TXT at _dmarc.domain.com).

​
Trace

Trace shows the chain of nameservers the query walks through to resolve a name. It starts at the root, hops to the TLD nameserver, then to the domain’s authoritative nameserver, then asks for the actual record. Useful for:
  • Confirming nameserver delegation: “Is my registrar pointing at the right NS?” Trace stops at the level that’s broken.
  • Diagnosing slow DNS: each hop’s response time is shown.

​
When to use it

Most users never need this page. Open it when:
  • You just changed an A or MX record and want to verify it’s live.
  • Your email is bouncing and you suspect SPF/DKIM/DMARC misconfiguration.
  • A site is loading on one network but not another (DNS propagation).
For “is propagation done?” outside your network, use a public tool like https://dnschecker.org instead. Track DNS only shows what the cPanel server sees.

​
Common questions

DNS responses are cached server-side based on the record’s TTL. The cPanel server might still hold a fresh-from-the-old-record cached answer. Wait the TTL out (default is often 300-3600 seconds) or query a specific external resolver from a real shell:
dig @8.8.8.8 mydomain.com +short
8.8.8.8 is Google’s resolver; 1.1.1.1 is Cloudflare’s. Different resolvers cache independently.
Their DNS resolver (their ISP’s, their browser’s local cache, or their device) is caching the old record. Time fixes it. To check from a visitor’s perspective, ask them to flush their DNS cache and retry, or test from a different network.
Either the records aren’t published yet, or the domain’s nameservers don’t have an MX record at all (which means the server defaults are used, or mail rejects). Check Zone Editor for what’s actually configured on Noxity-hosted domains; for domains hosted elsewhere, check the registrar/DNS provider.
Means the registrar’s NS records aren’t pointing at a working authoritative nameserver. Either the nameserver is down, or the registrar still has stale NS values from a previous host. Fix at the registrar’s domain panel.

​
Need a hand?