| Now we're finally ready to start building the servers. As we do this, we'll look at each boot file entry in more detail. It's worth noting a few points now that we have seen the example files: They refer to both primary/master and secondary/slave entries. The Version 4 file names them primary/secondary, while the newer Version 8 format refers to master/slave entries. We'll refer to them as master/slave. A master server for one domain may also be a slave for another, and vice versa. In other words, when we refer to the master and slave servers later, that is only for the domain we are configuring here.
Our Domain We currently have two subnets configured: one used by the internal facing machines, and a second used by the external facing machines. We will configure DNS so that only the 192.168.44.0 network is defined. This is for two reasons: To do this, we'll use the following machines as our name servers. Bear in mind that we have used a range of addresses reserved for private networks here (see Chapter 11, "Connecting to the Local Area Network") and that when you register a domain you will actually be assigned a range of IP addresses of your own to use (see Table 16.3). Table 16.3. Our DNS SettingsSetting | Value | Host Name |
|---|
Domain Name | Solarisbootcamp.com | | Master Name Server | 192.168.44.51 | antimony | Slave Name Server | 192.168.44.52 | tellurium |
If we check the hosts file, we'll see that we have two machines defined there, both built to our standard build in the same way as the rest of the systems as described in Chapter 11, "Connecting to the Local Area Network": antimony# grep DNS /etc/inet/hosts 192.168.44.51 antimony sb # master DNS server 192.168.44.52 tellurium te # slave DNS server antimony# | 
