DNS Explained

The internet's directory service that translates human-readable domain names into the IP addresses computers use to communicate.

DNS

The Domain Name System (DNS) is the internet's directory service that translates human-readable domain names (e.g., bookuvai.com) into machine-readable IP addresses (e.g., 93.184.216.34) so browsers can locate and connect to servers.

Explanation

Every device on the internet has an IP address, but humans remember names, not numbers. DNS bridges this gap. When you type a URL into your browser, a DNS resolver queries a hierarchy of servers — root servers, top-level domain (TLD) servers (.com, .org), and authoritative nameservers — to find the IP address associated with that domain. DNS records come in several types: A records (domain to IPv4 address), AAAA records (domain to IPv6 address), CNAME records (domain alias to another domain), MX records (mail server routing), TXT records (arbitrary text, used for verification and SPF/DKIM), and NS records (delegate to nameservers). TTL (time-to-live) values control how long resolvers cache each record. DNS is often called the "phone book of the internet," but it is also a critical performance and security component. DNS resolution adds latency to every new connection (typically 20-120ms). DNS-based attacks (DNS spoofing, DDoS on DNS infrastructure) can take entire services offline. DNSSEC adds cryptographic signatures to prevent spoofing, and DNS-over-HTTPS (DoH) encrypts DNS queries for privacy.

Bookuvai Implementation

Bookuvai manages DNS configuration as part of infrastructure provisioning, typically using Cloudflare or Route 53 via Terraform. We configure appropriate TTLs, set up DNSSEC where supported, and use DNS-based traffic routing for multi-region deployments. Domain verification records (SPF, DKIM, DMARC) for email deliverability are included in our standard setup.

Key Facts

  • DNS resolution typically adds 20-120ms to the first connection
  • There are 13 root server clusters operated by 12 independent organizations
  • DNS TTL values control how long records are cached by resolvers
  • DNSSEC adds cryptographic verification to prevent DNS spoofing
  • DNS-over-HTTPS (DoH) encrypts DNS queries for privacy

Related Terms

Frequently Asked Questions

Why does DNS propagation take time?
DNS changes are not instant because resolvers worldwide cache records based on TTL values. When you change a record, old cached versions persist until their TTL expires. Lower TTLs before changes to speed propagation.
What is a CNAME record?
A CNAME (Canonical Name) record creates an alias from one domain to another. For example, www.example.com might CNAME to example.com. CNAME records cannot coexist with other record types at the same name.
What is DNS-over-HTTPS?
DNS-over-HTTPS (DoH) encrypts DNS queries inside HTTPS connections, preventing ISPs and network operators from seeing which domains you resolve. Major browsers now support DoH with providers like Cloudflare (1.1.1.1) and Google (8.8.8.8).