The Domain Name System is the internet's distributed directory. It lets people type a name such as example.com while software connects to an IP address. DNS is not one giant database; it is a chain of delegated records and cached answers.
From a name to an answer
Your device asks a recursive resolver for a record. If the answer is not cached, the resolver follows referrals from root servers to the relevant top-level domain and authoritative name server. The final response is cached for the record's time-to-live period.
Records do different jobs
A and AAAA records point to IPv4 and IPv6 addresses. CNAME records create aliases, MX records direct email, and TXT records carry verification or email-security policies. A website can depend on several records even when visitors see only one name.
Why changes take time
DNS records include a TTL that tells caches how long to reuse an answer. Lowering it before a planned move can speed the transition, but resolvers and devices may still retain older information briefly. Propagation is usually a collection of expiring caches, not a switch copied around the world.
Privacy and encrypted DNS
Traditional DNS queries may be visible to the local network and resolver. DNS over HTTPS and DNS over TLS encrypt the path to the chosen resolver. They do not hide the destination from the website, and they shift trust toward the resolver operating that encrypted service.
Practical checklist
- Check A and AAAA records when a site behaves differently by network.
- Confirm authoritative name servers after moving DNS providers.
- Use sensible TTLs before and after planned changes.
- Choose a resolver with a clear security and retention policy.
Keep the result in context
Network tools provide useful evidence, not a complete identity or security verdict. Record what you tested, compare results before and after a change, and use several independent signals when a decision matters.
Browse all 25 KiwiVPN guides or return to the public IP checker.