DNS — the Domain Name System — is often called the phone book of the internet. It is the infrastructure that makes typing a domain name in your browser actually work.
How a DNS Lookup Works
When you type example.com into your browser, your browser checks its local cache first. If not cached, it queries your recursive resolver — typically your ISP’s DNS server or Google (8.8.8.8) or Cloudflare (1.1.1.1). The resolver queries a root nameserver which directs it to the appropriate TLD nameserver (.com, .net, etc.). The TLD nameserver directs it to the authoritative nameserver for example.com. The authoritative nameserver returns the A record — the IP address of the web server. All of this happens in milliseconds.
Key DNS Record Types
A Record maps a domain to an IPv4 address. CNAME creates an alias from one domain to another. MX records specify which server handles email for the domain. TXT records store arbitrary text used for domain verification, SPF, DKIM and DMARC. NS records specify the authoritative nameservers for the domain.
Why DNS Changes Take Time
Every DNS record has a TTL — the number of seconds resolvers should cache the record before checking for updates. Lowering your TTL to 300 before making changes speeds propagation significantly.
Need help managing your DNS records? Log into your client area for full DNS management.
