Technology10 min read

DNS in Depth: Resolution, Zones, DNSSEC & Anycast

A complete walkthrough of how the Domain Name System really works — the resolution chain, record types, DNSSEC integrity, encrypted DNS, and the Anycast architecture that makes it fast and resilient.

Published July 29, 2026Updated July 29, 2026
DNSDNSSECDNS ResolutionDNS RecordsAnycast DNSDoHDoTDNS over HTTPSZone FileSPF DKIM DMARCCAA RecordsRecursive Resolver

DNS is the internet's distributed directory — it translates human-friendly names like idenety.com into the IP addresses machines use. It's so fundamental that when DNS breaks, everything appears "down." This is the detailed guide.

The resolution chain

When a device needs www.idenety.com, the query passes through four roles:

  1. Recursive resolver — does the legwork and caches results (usually at your ISP or a public resolver like 1.1.1.1 or 8.8.8.8).
  2. Root servers (.) — refer the resolver to the correct TLD servers.
  3. TLD servers (.com) — refer to the domain's authoritative servers.
  4. Authoritative server — the source of truth that returns the actual record.

Each answer is cached for its TTL (Time To Live), so repeat lookups are instant until it expires.

Recursive vs. iterative vs. authoritative

  • Recursive query: "Get me the final answer" — the resolver keeps asking on your behalf.
  • Iterative query: each server returns a referral to the next server.
  • Authoritative answer: comes from the server that holds the zone, not from cache.

The zone file & record types

RecordPurposeCommon use
A / AAAAName → IPv4 / IPv6 addressPoint domain to server
CNAMEAlias one name to anotherwww → apex, CDN hostnames
MXDirects email to mail servers (priority-ordered)Microsoft 365, Google Workspace
NSDelegates the zone to authoritative serversNameserver delegation
SOAStart of Authority — serial, refresh, default TTLZone metadata
TXT / SPFText records; authorize mail sendersEmail authentication
DKIMPublic key to verify signed outbound mailEmail integrity
DMARCPolicy for SPF/DKIM failures + reportingEmail fraud prevention
SRVLocates services (SIP, Autodiscover)VoIP, Teams, Exchange
CAADeclares which CAs may issue TLS certsCertificate issuance control

DNSSEC — integrity & authenticity

Plain DNS can be spoofed via cache poisoning. DNSSEC cryptographically signs records (RRSIG) and validates them up a chain of trust from the root — guaranteeing the answer wasn't tampered with. Note it provides integrity, not confidentiality.

Encrypted DNS: DoH & DoT

Traditional queries are plaintext and visible to anyone on the path. DoT (DNS over TLS, port 853) and DoH (DNS over HTTPS, port 443) encrypt them for privacy — critical for roaming users and zero-trust environments.

Anycast — the architecture behind fast, resilient DNS

With Anycast, the same IP is announced from many global locations via BGP, so each user is routed to the nearest, healthiest node. See our Anycast guide for the full architecture.

Common pitfalls IDENETY fixes: orphaned records after a host migration, TTLs left too high before a cutover, DMARC stuck in "monitor only," and missing CAA records that let any CA issue certificates for your domain. Download the full reference: IDENETY DNS and Edge Architecture (PDF).

Contact our engineers to discuss DNS architecture, DNSSEC implementation, or email authentication hardening.