| Now that we have the master and slave servers functioning correctly, we can configure the remaining clients to perform host name lookups. These are very easy to set up; in fact, we have already done this in Chapter 13, "Connecting to the Internet." The only difference is that the name servers we'll be using are the local ones we've just configured. Let's use xenon as an example machine to see the changes we've made. First we'll create the resolver configuration file, which contains the addresses of the name servers we wish to usethis will be copied from the master as we said earlier: iodine# cat /etc/resolv.conf ; ; resolv.conf that queries the ; master name server first, followed ; by the slave name server ; search solarisbootcamp.com nameserver 192.168.44.51 nameserver 192.168.44.52 iodine# Now, we can run through a few nslookup checks to make sure the servers are responding with a valid answer. We don't need to carry out all the testswe just need to make sure we get the answers in a reasonable amount of time: iodine# nslookup www.sun.com Server: antimony.solarisbootcamp.com Address: 158.43.128.72 Non-authoritative answer: Name: www.sun.com Address: 192.18.97.241 iodine# Next we can update the switch file to start performing host name lookups: iodine# grep hosts /etc/nsswitch.conf hosts: files dns iodine# As a final test, we'll run another ping check so we're happy everything is set up correctly: iodine# ping www.sun.com www.sun.com is alive iodine# | 
