When “Nameserver” and “DNS Resolver” Mean Different Things

DNS terminology is full of words that shift meaning depending on context. Two of the most common—nameserver and DNS resolver—each refer to multiple distinct concepts. If you already understand DNS, you can usually tell which sense is meant from context. For someone still learning, that ambiguity is a genuine source of confusion.

The Two Senses of “Nameserver”

In one context, a nameserver is an authoritative nameserver. This is the server where a domain’s DNS records are stored and updated. It’s the sense used when talking about a specific domain, such as:

  • Instructions to “connect a domain you already own by changing its name servers”
  • Notes that domains typically rely on multiple nameservers for reliability, so queries can fall back if one fails
  • Guidance for updating nameserver records through your domain registrar

In another context, a nameserver is a recursive nameserver, also called a DNS resolver. This is the server your computer or browser actually contacts. It resolves the query by finding the right authoritative nameserver, retrieving the record, and caching the result. This sense appears when discussing your own browsing setup, for example:

  • Complaints about how changing nameservers on Windows 10 takes multiple clicks
  • Advertisements for public nameservers like 1.1.1.1, 1.0.0.1, and 9.9.9.9
  • Instructions to configure your device to use 8.8.8.8 and 8.8.4.4 as your DNS servers

“DNS Resolver” Can Be a Library or an Entire Server

The term DNS resolver is even messier: it can mean a library, a forwarding server, or a full recursive server.

Stub resolver as a library. A stub resolver is a component—often a library—that does not know how to resolve DNS names on its own. It merely forwards queries to a real resolver. For instance, libc’s getaddrinfo function looks at /etc/resolv.conf and passes the query along to whatever DNS server is listed there. You’re dealing with this kind of resolver if it’s part of your operating system or a library. Common usage:

  • “The resolver is a set of routines in the C library that provide access to DNS”
  • References to resolvers that try a list of configured DNS servers one by one until one works
  • Messages like “Successfully flushed the DNS Resolver Cache”

Stub resolver as a server. Some stub resolvers are not libraries but servers. Examples include systemd-resolved and dnsmasq, the latter often running on your router. This kind is also called a DNS forwarder. If it’s running on your router or shipped with your OS, it’s almost certainly a stub resolver.

Recursive nameserver. In the server sense, a “DNS resolver” is a recursive nameserver that actually knows how to track down authoritative nameservers and assemble an answer. This is the kind you’re dealing with if the software is unbound or bind, or if the IP is something like 8.8.8.8 or 1.1.1.1, or if it’s operated by your ISP. Examples:

  • “The DNS Resolver in pfSense® software utilizes unbound, which is a validating, recursive, caching DNS resolver…”
  • “We invite you to try Google Public DNS as your primary or secondary DNS resolver…”
  • “We are in the process of implementing our own DNS resolver…”

Which Terms Actually Get Used

A quick, informal check of Google hit counts suggests that the generic terms dominate:

  • dns server: 8,000,000
  • nameserver: 4,200,000
  • dns resolver: 933,000
  • public DNS server: 204,000
  • root nameserver: 42,000
  • recursive resolver: 38,500
  • stub resolver: 26,100
  • authoritative nameserver: 17,000
  • dns resolution service: 9,450
  • TLD nameserver: 7,500
  • dns recursor: 5,300
  • recursive nameserver: 5,060

The takeaway: “nameserver” and “DNS resolver” are by far the most widely used terms, while the more precise labels—authoritative nameserver, recursive nameserver, stub resolver—are comparatively rare. That gap makes the ambiguity hard to avoid, but understanding the possibilities makes it easier to interpret what someone actually means.