Quick Summary
The term “DNS” covers several server roles, but most user-facing discussions are really about recursive resolvers such as Cloudflare, Google, or Quad9.
Technical explanation
| DNS type | Role in the lookup |
|---|---|
| Recursive resolver | Accepts the user’s query and finds the answer |
| Root nameserver | Directs the resolver to the right top-level domain |
| TLD nameserver | Directs the resolver to the correct authoritative server |
| Authoritative nameserver | Returns the official record for the domain |
DNS records are also often grouped by purpose. For example, A and AAAA records point to IP addresses, MX handles mail routing, and CNAME creates an alias. That record-level view is different from the server-role view above.
Real-world examples
- Switching from ISP DNS to Cloudflare changes your recursive resolver.
- Moving a domain to a new DNS hosting provider changes the authoritative layer.
- Blocking malicious domains at a security resolver affects resolution at the recursive stage.
For the broader mechanism, read what DNS is. If your interest is security rather than architecture, continue with DNS spoofing or is DNS safe.
