DNS (Domain Name System) is the internet's address book — the system that translates human-readable domain names like google.com into the numeric IP addresses (like 142.250.80.46) that computers use to find each other on the network. Every time you type a URL into your browser, send an email, or use any internet-connected application, a DNS query happens behind the scenes to convert the domain name into an IP address your device can connect to.
DNS operates as a distributed hierarchical system. When you look up a domain, the query starts at your local DNS resolver (usually provided by your ISP or a service like Cloudflare or Google), which checks its cache. If the answer isn't cached, the resolver queries the root DNS servers, which direct it to the appropriate top-level domain (TLD) servers (.com, .org, .net), which in turn point to the domain's authoritative nameservers — the servers that hold the actual DNS records for that specific domain. This entire chain of queries typically completes in under 100 milliseconds.
DNS Record Types
Different DNS record types serve different purposes. Understanding what each type does helps you diagnose issues and configure domains correctly:
A Record – The most fundamental record type. Maps a domain name to an IPv4 address. When someone visits your website, the A record tells their browser which server to connect to.
AAAA Record – The IPv6 equivalent of an A record. Maps a domain to an IPv6 address. As IPv6 adoption grows, more domains are adding AAAA records alongside their A records.
MX Record – Specifies the mail servers responsible for receiving email for the domain, including priority values that determine which server is tried first. Essential for email delivery — incorrect MX records mean email to your domain will bounce.
NS Record – Identifies the authoritative nameservers for the domain. These are the servers that hold the definitive DNS records and respond to queries about the domain.
TXT Record – Contains arbitrary text data, most commonly used for email authentication (SPF records that specify which servers can send email for your domain, DKIM signatures for email verification, and DMARC policies that tell receiving servers how to handle authentication failures), as well as domain ownership verification for services like Google Search Console.
CNAME Record – Creates an alias that points one domain name to another. For example, www.example.com might have a CNAME record pointing to example.com, so both resolve to the same server. CNAMEs cannot coexist with other record types on the same name.
SOA Record – The Start of Authority record contains administrative information about the DNS zone, including the primary nameserver, the administrator's email address, the zone serial number, and timing parameters for zone transfers and caching.
Common Uses for DNS Lookup
DNS lookup tools are essential for anyone managing websites, email systems, or network infrastructure:
Troubleshooting DNS Propagation – After changing DNS records (like moving to a new web host), lookups verify whether the changes have propagated. DNS changes can take anywhere from minutes to 48 hours to fully propagate depending on TTL values.
Email Configuration – Checking MX records confirms that email is routed to the correct mail servers. Misconfigured MX records are one of the most common causes of email delivery failures.
Email Authentication – Verifying SPF, DKIM, and DMARC records in TXT entries ensures your email authentication is configured correctly, which directly impacts email deliverability and protects against spoofing.
Website Migration – Before and after migrating a website, DNS lookups confirm that A records point to the new server and that no records were accidentally changed or deleted during the transition.
Security Investigation – Looking up DNS records for suspicious domains can reveal information about the infrastructure behind phishing sites, spam sources, or malicious servers.
TTL (Time To Live)
Every DNS record includes a TTL value, measured in seconds, that tells DNS resolvers how long they can cache the record before checking for updates. A TTL of 3600 means resolvers will cache the record for one hour. Lower TTL values (like 300 seconds) mean changes propagate faster but generate more DNS queries. Higher TTL values (like 86400 seconds — one day) reduce query volume but mean changes take longer to reach all users.
When planning DNS changes, it's good practice to lower the TTL well in advance (at least 24-48 hours before the change) so that when you make the update, the old cached records expire quickly. After the change is confirmed working, you can raise the TTL back to a higher value. For a deeper dive into how DNS works end-to-end, see our article on DNS explained.