Configuring and Managing MPE/iX Internet Services (MPE/iX 6.5)

140 Chapter8
DNS BIND/iX
DNS BIND Troubleshooting Steps
Figure 8-1 Labeling Nodes
5. Configuration Gathering: Once you have a good understanding of
the history, symptoms, and topology, it’s time start examining the
DNS configuration at the site. Relying on assumptions does not work
with DNS BIND troubleshooting.
This information is needed from each system.
• From ALL Systems:
a. Review the following files:
/etc/resolve.conf
/etc/nsswitch.conf (If present)
results for all lan interfaces
b. Run the following commands:
nettool.net.sys “conf;summ;gui”
linkcontrol@,S
netcontrol <NIname>;STATUS for each appropriate NI
c. From Nameservers:
All the information detailed above in “From ALL
Systems”
/etc/named.conf (Or the customers equivalent)
The system’s db files
Look in the /etc/named.conf file and the directory directive will
tell you where to look for these. They are prefixed with db or zone, so
may look like these examples:
db.cache, db.root, db.127.0.0,. db.cup, etc.
6. Configuration Validation: Once the configuration information is
gathered, it’s time to sit down and wade through it all, looking for
problems. By now you should have a good idea of how this DNS
BIND topology fits together. Consider the symptoms, the history, the
topology, and verify the levels of configuration that might be
responsible for these problems.
server1.cup.hp.com
IP Addr: 15.1.1.1
Function: Primary Nameserver
server2.cup.hp.com
IP Addr: 15.1.1.2
Function: Secondary Nameserver
foo.cup.hp.com
IP Addr: 15.1.1.3
Function: DNS User