DNS

DNS, the Domain Name System, is the distributed, hierarchical naming system that turns human-readable domain names like example.com into the IP addresses machines actually route to. Standardized in RFC 1035 and layered on ever since, it is the quiet lookup that happens before every API call, page load, and email. Nothing on the modern internet reaches its destination without it.

• Hierarchical resolution - Root, top-level, and authoritative servers resolve a name step by step, distributing the load across the whole internet.
• Record types - A, AAAA, CNAME, MX, TXT, and SRV records map names to addresses, mail servers, and metadata.
• Caching and TTLs - Time-to-live values let resolvers cache answers, trading freshness for speed and resilience.
• A programmable control plane - Providers like Cloudflare, Route 53, and DNSimple expose DNS management as an API, making records first-class infrastructure-as-code.

In real API operations DNS is where an API’s public presence begins — the api. or developer. subdomain a team stands up is a DNS record, and how that name resolves shapes routing, rate limiting, failover, and even where security researchers look first. It is also a governance signal: a clean, well-managed domain with sensible records and TLS reads as operational maturity, while the well-known /.well-known/ paths that agents and crawlers probe all hang off a name that DNS has to resolve. As more traffic becomes machine-to-machine, DNS remains the first hop every agent takes before it can talk to an API at all.