Everything you need to know about the Domain Name System, DNS records, domain resolution, propagation, and network diagnostics. The definitive resource for webmasters and network admins.
Our DNS Lookup tool fetches records directly in real-time. We use native backend DNS resolution libraries and direct UDP port 53 queries against public recursors (like Cloudflare 1.1.1.1 and Google 8.8.8.8) to ensure you are seeing live DNS propagation states without the interference of localized browser caching. This gives you an accurate, unbiased look at how the global internet sees your domain.
The Domain Name System (DNS) is universally referred to as the "phonebook of the Internet." Humans access information online through readable domain names, like google.com or freeseomate.com. However, web browsers interact through Internet Protocol (IP) addresses.
DNS translates those human-friendly domain names into machine-readable IP addresses so browsers can load internet resources. Each device connected to the Internet has a unique IP address that other machines use to find the device. DNS servers eliminate the need for humans to memorize complex numeric IP addresses such as 192.168.1.1 (in IPv4), or newer, more complex alphanumeric IP addresses like 2400:cb00:2048:1::c629:d7a2 (in IPv6).
Without DNS, you would have to maintain a local ledger of IP addresses for every website you ever wanted to visit, making the modern, scalable internet impossible.
The process of DNS resolution involves converting a hostname into a computer-friendly IP address. When a user requests a webpage, a translation must occur between what the user types into their browser and the machine-friendly address necessary to locate the webpage.
In a typical DNS lookup, the query follows a strict, hierarchical path:
8.8.8.8)..com or .org). The TLD server holds information for all domains sharing that common extension.Using our DNS Lookup tool is incredibly simple, yet provides expert-level diagnostics.
example.com) into the search bar. Do not include https:// or www..DNS records are database instructions that provide information about a domain, including its IP address, how to handle mail, and verification security rules. Here are the most critical records our tool analyzes:
The core record that maps a domain name directly to a physical IPv4 address (e.g., 192.0.2.1). It is the mechanism that directs a user's browser to your web server.
Functions exactly like an A record, but it points to an IPv6 address (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). As the internet transitions to IPv6 due to IPv4 exhaustion, AAAA records are increasingly vital.
Creates an alias, mapping one domain name to another instead of directly to an IP address. For example, www.example.com often has a CNAME pointing to the root example.com. (Note: A CNAME cannot be placed at the root apex of a domain).
Specifies the mail servers responsible for accepting email messages on behalf of a recipient's domain. MX records include a "priority" value—the lowest number is the highest priority server.
Originally intended for human-readable notes, TXT records are now heavily utilized for machine-readable security policies. Crucial uses include:
Indicates which DNS servers are authoritative for a domain. NS records perform the act of "delegation"—telling the world exactly who is managing the zone file for this domain name.
Stores administrative information about the domain's DNS zone, including the primary nameserver, the email of the domain administrator, the domain serial number (used to track zone updates), and timers specifying how often secondary servers should refresh.
A security record that specifies exactly which Certificate Authorities (like Let's Encrypt or DigiCert) are allowed to issue SSL/TLS certificates for the domain. It prevents rogue CAs from issuing fraudulent certificates.
Provides Reverse DNS logic. While an A record maps a domain to an IP, a PTR record maps an IP address back to a domain. This is primarily used as a security and anti-spam measure for validating mail servers.
Specifies the host and port for specific services. Common in enterprise environments (like Microsoft Active Directory) and protocols like SIP/VoIP to discover services without needing dedicated subdomains.
DNS resolution is highly decentralized. To troubleshoot DNS effectively, you must understand the distinction between the four types of servers involved in the global infrastructure.
The recursive resolver (or DNS recursor) is the middleman. It receives the initial query from your web browser and is responsible for making all the subsequent requests to find the final IP address. It aggressively caches data to speed up future requests. (Examples: Google 8.8.8.8, Cloudflare 1.1.1.1, or your ISP's default servers).
There are 13 logical root name servers globally (operating via Anycast across hundreds of physical servers). They sit at the very top of the DNS hierarchy. They don't know the IP addresses of websites; they only know which TLD servers to point the resolver toward.
The Top-Level Domain (TLD) servers maintain information for all domains that share a common extension (like .com, .org, or .uk). If you query example.com, the .com TLD server responds with the Authoritative Name Servers specifically assigned to example.com.
The Authoritative Name Server is the bottom of the chain. It actually holds and maintains the DNS records (A, MX, TXT) for the specific domain. When you update your DNS settings at Cloudflare, Route53, or GoDaddy, you are updating the Authoritative Name Server.
When you change a DNS record, the change is instantly reflected on your Authoritative Name Server. However, users globally might not see the change immediately. This delay is known as DNS Propagation. It occurs because recursive resolvers worldwide have cached your old DNS records to save time and bandwidth.
TTL is the amount of time (in seconds) that a DNS record is permitted to be cached by a recursive resolver before it must throw the data away and query the authoritative server again.
If a website goes down or emails stop delivering, DNS is often the culprit. Here are the most frequent scenarios:
Cause: The domain is expired, missing an A record, or the nameservers were incorrectly removed.
Solution: Use this tool to query the NS records. If none return, log into your registrar to fix the nameserver delegation.
Cause: You changed web hosts but the A record still points to the old server, or propagation hasn't finished.
Solution: Check the TTL value on the A record. Wait for the cache to clear, or flush your local OS DNS cache.
Cause: Your business emails are bouncing. Your MX records were likely overwritten or deleted during a web host migration.
Solution: Run an MX lookup. If empty, you must re-add your Google Workspace, Microsoft 365, or host-specific MX records immediately.
Cause: A CNAME points to another CNAME which points to a dead end (or creates an infinite loop).
Solution: Ensure your CNAME resolves to an A record as quickly as possible. Never place a CNAME at the root apex (@) of a domain.
DNS was originally designed without built-in security, making it vulnerable to various attacks.
DNSSEC (Domain Name System Security Extensions) retrofits security onto DNS. It does not encrypt DNS queries, but it adds cryptographic signatures to existing DNS records (using RRSIG, DNSKEY, and DS records).
When a recursive resolver queries a DNSSEC-enabled domain, it verifies the cryptographic signature. If the signature is missing or invalid, the resolver knows the data was tampered with and will block the user from visiting the compromised IP address.
Verify that your A records have successfully propagated to a new IP address after launching a new website.
Troubleshoot bouncing emails by verifying that MX, SPF, DKIM, and DMARC TXT records are correctly formatted and resolving.
Verify that CNAME records are properly pointing to your Content Delivery Network (like Cloudflare or Fastly).
Ensure that subdomains correctly resolve and that DNS downtime isn't causing Googlebot to drop your indexed pages.
If a website is entirely unavailable, follow this strict diagnostic hierarchy: