Domain Name System
Subject: Computer and Technology noun /doʊˈmeɪn neɪm ˈsɪs.təm/ 1 definition
- computer-networking
- internet-protocols
- distributed-systems
- web-infrastructure
-
Definition (noun)
Entry #11 · UpdatedThe Domain Name System (DNS) is the internet's hierarchical, decentralized naming directory that translates human-readable domain names into numerical IP addresses and routing metadata required by network protocols. Operating across distributed zones—from root servers and top-level domain (TLD) registries down to authoritative name servers—it relies on recursive resolvers and time-to-live (TTL) caching to resolve lookups rapidly at global scale. Rather than transporting application payloads or hosting web content itself, DNS functions purely as a foundational control-plane lookup layer that decouples logical service names from underlying network addresses.
Common Types
Authoritative DNS: Hosts the official zone files and resource records (
A,AAAA,CNAME,MX,TXT) for a domain, serving as the final source of truth for resolution queries.Recursive DNS: Accepts lookup requests from client stub resolvers and traverses the DNS hierarchy—from root and TLD name servers to authoritative servers—while caching responses according to each record's TTL.
Private (Split-Horizon) DNS: Resolves internal hostnames exclusively within a corporate network or cloud Virtual Private Cloud (VPC), keeping private service endpoints unreachable from the public internet.
Encrypted DNS (DoH and DoT): Protects query privacy and integrity over untrusted networks by encapsulating DNS messages inside HTTPS (DNS over HTTPS) or TLS (DNS over TLS) connections rather than plaintext UDP.
Example
When a developer enters
api.example.cominto a browser without a cached entry, the local recursive resolver queries a root server, follows its referral to the.comTLD name server, and queriesexample.com's authoritative server to obtain anArecord pointing to203.0.113.42with a 300-second TTL. The browser then opens a TCP connection to that IP address while the resolver caches the mapping for five minutes so subsequent requests resolve immediately.