Authoritative Nameserver
A nameserver that holds the original, definitive DNS records for a domain, as opposed to a cached copy.
An authoritative nameserver is the server that holds the original DNS records for a domain in its zone file. When a recursive resolver chases a query down through the DNS hierarchy (root, then TLD, then domain), the answer it ultimately reaches comes from the authoritative nameserver for that domain. Authoritative responses set the AA flag in the DNS reply, signalling that the data is canonical rather than cached. If a domain's authoritative nameservers go down or return wrong data, the domain effectively disappears from the internet. Most domains run at least two authoritative nameservers for redundancy.
Reference
Related terms
See also
Referenced on
- 25 DNS Jokes Every SysAdmin Will Painfully Relate To
- Complete Guide to DNS Attacks and DNS Security (Prevention, Testing & Mitigation)
- DNS Lookups in PHP: dns_get_record, gethostbyname, and Beyond
- DNS Lookups in Python: Complete Guide with dnspython
- DNS Propagation Checker
- DNS Propagation Myths Debunked: It's Really About Cache Freshness
- DNS Providers
- DNS Rebinding Attack: How Browsers Are Tricked Into Bypassing Same-Origin Policy
- DNS Troubleshooting Tools: What the Pros Actually Use
- DNS Tunneling Attack: How Data Is Smuggled Through Port 53
- DNS Water Torture Attack: How Random Subdomain Floods Overwhelm Nameservers
- Home
- How DNS Queries Work: A Developer's Guide to the DNS Protocol
- How to Verify DNS Changes After Switching Hosting Providers
- HTTP Header Checker
- NXDOMAIN Attack: How Nonexistent Domain Floods Exhaust DNS Resolvers
- The Complete dig Command Guide: Every Flag and Option Explained
- Top DNS Providers by Market Share
- Troubleshooting Common DNS Issues: A Step-by-Step Guide
- Understanding DNS Record Types: A, AAAA, CNAME, MX, TXT, and More
- What Is DNS Propagation and Why Does It Take So Long?
- What Is DNS TTL? How Time to Live Controls Caching, Propagation, and Performance
- What Is NXDOMAIN? Understanding the 'Domain Does Not Exist' DNS Response