DNS Lookup
Look up DNS records for any domain: A, AAAA, MX, TXT, CNAME, NS, and SOA records.
Embed this toolAdvertisement
Understanding the Domain Name System
The Domain Name System (DNS) is one of the most critical infrastructure components of the modern internet. Operating as a distributed database organized in a tree-like hierarchy, DNS maps human-friendly domain names to the numerical IP addresses that computers use to communicate. Without DNS, the user experience of browsing the web would be drastically different, requiring users to memorize long strings of numbers for every service they access.
DNS was designed to be decentralized and resilient. No single server stores all domain records; instead, the namespace is divided into zones managed by different organizations. At the top of the hierarchy are the root servers, followed by Top-Level Domain (TLD) servers for extensions like .com, .org, and .net, and finally the authoritative name servers operated by domain registrants and hosting providers.
DNS Resolution Process
When you type a URL into your browser, a multi-step resolution process begins. Your device first checks its local cache and hosts file. If no match is found, it sends a query to a recursive resolver, typically provided by your ISP or a public service like Google DNS (8.8.8.8) or Cloudflare (1.1.1.1). The recursive resolver then traverses the DNS hierarchy: root → TLD → authoritative, caching answers along the way to speed up future requests.
Common DNS Record Types
DNS stores data in resource records, each with a specific type and purpose. A and AAAA records map domains to IPv4 and IPv6 addresses. CNAME records create aliases. MX records direct email traffic. TXT records hold verification and policy strings. NS records delegate zones to authoritative servers. SOA records define zone administrative parameters. PTR records enable reverse DNS lookups, mapping IP addresses back to hostnames.
TTL & Propagation
Every DNS record has a Time To Live (TTL) value that controls how long resolvers may cache it. When you change a DNS record, the old value remains cached until the TTL expires across all recursive resolvers that have queried it. This is why DNS changes do not take effect instantly and why planning ahead with conservative TTL values is important before making critical infrastructure changes.
External References
Related NerdsTips Tools
For quick reference on IP addressing, check out our Subnet Mask Table for a complete CIDR cheat sheet. If you need to decompose URLs into their protocol, host, path, and query components, try our URL Parser tool.