The term resolver can be used in three distinct ways:
As a generic term to describe any entity software/hardware that resolves names to IPs.
More specifically it refers to a set of functions supplied as part of the standard C network/socket libraries (for example, glibc6 in *nix systems) or supplied as part of a package (for example, BIND). These functions are used by applications to answer questions such as 'what is the IP address of this host'. The most common method to invoke such resolver services, used by your browser among many other applications, is to use the POSIX socket functions 'gethostbyname' (or 'getaddrinfo' for sock2) for name to IP and 'gethostbyaddr' (replaced by 'getnameinfo' in sock2) for IP to name. Typically the term 'resolver library' may be applied to this functionality. Every system that accesses the internet (for instance a desktop PC or a mobile device) has a resolver library or resolver functionality.
The term resolver is also used to describe a DNS system whose function, uniquely, is to resolve DNS queries on behalf of clients such as desktop PCs or modile devices. Such a resolver, which may also be called a Caching Name Server or an area resolver, is typically located in a ISP, cellco or large corporate network. The Resolver in this case is hardened against external network attacks, normally contains a huge cache to increase performance for its clients and provides recursive (it can follow referrals) functionality to its clients.
Resolvers are quite complicated and are defined to be capable of following referrals (they can work with systems that do not support recursive queries. However, on desktop and mobile devices almost all resolvers (both Windows and *nix) are stub resolvers. A stub resolver is a minimal resolver which will only work with a DNS (an area resolver) that does support recursive queries, specifically stub-resolvers cannot follow referrals. Modern destop PC and mobile devices now provide what is called a caching resolver. This resolver is a stub resolver but it does maintain a cache of responses to minimize network access and increase performance.
There are a number of ways your system can resolve a name and the actual order will vary based on your configuration:
If you are using a *nix system with the GNU glibc libraries the order of lookup is determined by the 'hosts' entry in the /etc/nsswitch.conf file which will read something like:
hosts files nisplus dns
Indicating look at /etc/hosts, then use NIS (Network Information Systems), then DNS (via resolv.conf)
If you are using a *nix system with the older GNU libc libraries the order of lookup is determined by the 'order' entry in the /etc/host.conf file which will read something like:
Indicating look at /etc/hosts then DNS (using resolv.conf)
If you are using a windows system the order is:
hosts dns files
Which means use DNS (via resolve.conf) then /etc/hosts.
Problems, comments, suggestions, corrections (including broken links) or something to add? Please take the time from a busy life to 'mail us' (at top of screen), the webmaster (below) or info-support at zytrax. You will have a warm inner glow for the rest of the day.
3 reverse map
4 dns types
5 install bind
8 zone records
12 bind api's
13 dns security
bits & bytes
notes & tips
This work is licensed under a Creative Commons License.
If you are happy it's OK - but your browser is giving a less than optimal experience on our site. You could, at no charge, upgrade to a W3C STANDARDS COMPLIANT browser such as Firefox