When you type a domain name into your browser, the computer does not inherently know the IP address of that server. It asks the Domain Name System (DNS) to translate the name into an IP address. This lookup happens behind the scenes in milliseconds, but understanding how it works is essential for debugging email delivery problems, verifying domain configurations, and diagnosing connectivity issues.
How DNS Resolution Works
Your computer has a DNS resolver (usually provided by your ISP or set to a public resolver like 8.8.8.8 or 1.1.1.1). When you request example.com, the resolver asks a root name server which name server is authoritative for .com domains. The root server directs the resolver to the .com TLD (top-level domain) servers. The TLD server directs the resolver to the name servers specified in the domain's registrar record. Those authoritative name servers return the actual DNS records for example.com. The resolver caches the result for the TTL (time to live) specified in the record.
This hierarchical lookup takes a fraction of a second and is cached at multiple levels to keep subsequent lookups fast.
DNS Record Types
The A record maps a domain name to an IPv4 address. This is the most fundamental record type.
The AAAA record maps a domain name to an IPv6 address.
The CNAME (Canonical Name) record creates an alias from one domain name to another. A CNAME for www.example.com might point to example.com, redirecting all queries to the same IP address.
The MX (Mail Exchange) record specifies the mail servers that receive email for the domain. MX records have a priority value; lower numbers are tried first.
The TXT record holds arbitrary text. It is used for domain ownership verification, SPF records (which IP addresses are allowed to send email on behalf of the domain), DKIM public keys (for email signature verification), and DMARC policies.
The NS (Name Server) record specifies the authoritative name servers for the domain.
The SOA (Start of Authority) record contains administrative information about the zone including the primary name server and the email address of the zone administrator.
Using the DevHexLab DNS Lookup Tool
Open the tool at /tools/developer/dns-lookup. Enter a domain name. Select the record type. The tool returns the current records from the DNS system. This is useful for verifying that DNS changes have propagated, diagnosing email delivery failures, and auditing domain configurations.
Frequently Asked Questions
Why is my DNS change not taking effect?
DNS changes propagate gradually based on TTL values. If the old record had a TTL of one day, resolvers that cached it will keep using the old value for up to 24 hours. Lower the TTL before making a planned change to speed up propagation.
What is a wildcard DNS record?
A wildcard record like *.example.com matches any subdomain that does not have a more specific record. Any request for anything.example.com returns the wildcard result.
How do I verify my SPF record is set up correctly?
Query the TXT records for your domain and look for a record starting with v=spf1. It lists the IP addresses and services authorised to send email from your domain.
Understanding DNS turns mysterious domain configuration into something logical and debuggable.