- 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 Server Architecture
DNS supports a hierarchal namespace and replica or caching servers. The namespace is separated into zones that can have primary and secondary servers. Primary servers act as masters from which information is updated and then pushed out to the secondary servers.
The Berkeley Internet Name Domain (BIND) is the name server (named) that runs on a designated host in your organization. Since there are different features that are available in different versions, it is helpful to know what version you are running. TABLE 2-4 correlates the BIND version with the Solaris operating environment that it appears in.
TABLE 2-4 Solaris Versions of BIND
Solaris OE Version |
BIND Version |
SunOS 4.x |
4.8.1 |
SunOS 2.0-2.5 |
4.8.3 |
SunOS 2.6 4.9 |
4-P1 |
SunOS 5.7 |
8.1.2 |
SunOS 5.8 |
8.1.2 |