- Evolution of Solaris Naming Services
- NIS and Files Coexistence
- NIS and DNS Coexistence
- Solaris Naming Service Switch
- Solaris Naming Service Switch Architecture
- NIS Architecture Overview
- NIS Client Server Architecture
- How NIS Clients Bind to the NIS Server
- NIS Maps
- NIS High Availability Architecture Features
- NIS+ Architecture Overview
- NIS+ Client Server Architecture
- How NIS+ Clients Bind to the NIS+ Server
- NIS+ Tables
- NIS+ Interaction with DNS
- NIS+ High Availability Architecture Features
- Solaris DNS Architecture Overview
- DNS Client Architecture
- DNS Server Architecture
- DNS High Availability Features
- LDAP Architecture Overview
- LDAP Information Model
- LDAP Naming Model
- LDAP Functional Model
- LDAP Security Model
- LDAP Replication
- Comparison with Legacy Naming Services
DNS Client Architecture
Solaris system utilities that access DNS do so by using the resolver on the client. The resolver is actually a set of library routines that perform various types of queries. These queries get information about the location of the DNS servers by looking in the /etc/resolv.conf file. The following shows the format of this file:
As you can see, more than one DNS server can be specified. In normal operation the resolver tries to contact the first server in the list. If contact cannot be established, the second server is tried, then the third. The current limit in the Solaris operating environment is three.