After navigating root and TLD servers, you still don’t have the IP address. Someone needs to hold the actual DNS records (A, AAAA, CNAME, etc.) for each domain—that’s the authoritative server.
The authoritative server is the final authority for a domain—it holds the actual DNS records (A, AAAA, MX, etc.) and returns the real IP address. This is the server operated by the domain owner or their DNS provider.
- Query from Resolver: “What is the IP for google.com?”
- Lookup: Authoritative server checks its zone file
- Response: Returns the A record (IPv4) or AAAA record (IPv6)
- Example: “google.com = 142.250.183.46”
- Done: Resolver caches and returns IP to client
The domain owner configures records on their authoritative server (or via DNS provider like Cloudflare, AWS Route53).
- Holds actual DNS records (A, AAAA, CNAME, MX, TXT, etc.)
- Domain owners configure records via their DNS provider
- Responds authoritatively—no further lookup needed
- Can be primary (master) or secondary (slave) for redundancy
- Built from: DNS TLD Server — TLD points to authoritative server
- Builds into: DNS Lookup — authoritative gives the final answer
- Related: DNS Records — authoritative servers store these
- Related: DNS Zone — the configuration file holding records
- Misconfigured records cause site outages
- TTL affects how long resolvers cache the answer
- Secondary servers sync from primary (zone transfer)
- Anycast used by large providers for global coverage