A distributed directory
People remember names such as hideout64.org; networks deliver packets to IP addresses. DNS connects these two worlds. It is not a single database: it is a distributed hierarchy of zones, served by many authoritative name servers.
Applications usually ask a recursive resolver for the records they need. The resolver may answer from cache. Otherwise, it follows referrals through the DNS hierarchy until it reaches a server authoritative for the relevant zone.
The records you see most often
| Type | Purpose |
|---|---|
A |
IPv4 address |
AAAA |
IPv6 address |
CNAME |
Alias to another DNS name |
MX |
Mail exchangers for a domain |
TXT |
Arbitrary text often used for verification or email policy |
DNS answers can include multiple values, and a client may choose between them. DNS does not itself decide which web page to show; that happens later in the HTTP exchange.
What TTL really means
A Time to Live (TTL) tells caching resolvers how long a record can generally be reused before it needs refreshing. When a record changes, some resolvers may keep the old answer until their cached TTL expires. That is why a DNS change may seem immediate from one network and delayed from another.
The popular phrase “DNS propagation” is misleading: there is no universal broadcast that updates every resolver at once. Cache expiry and delegation updates explain much of the observed delay.
Privacy, integrity and troubleshooting
DNSSEC lets validating resolvers verify the authenticity of signed DNS data; it does not encrypt DNS queries. DNS over HTTPS (DoH) and DNS over TLS (DoT) encrypt the link to the chosen resolver, but the resolver still handles your questions.
On Windows, inspect records with:
Resolve-DnsName hideout64.org -Type A
Resolve-DnsName hideout64.org -Type AAAA
On Linux, dig hideout64.org A offers a similar starting point. For troubleshooting, compare answers from the expected authoritative DNS servers and your usual resolver.