Technical data

Configuring and Managing BIND
5.9 Solving Bind Server Problems
5.9.1 Server Not Responding
A missing client name in the BIND server’s database files results in lack of
service to that client. If records that point to the name servers (NS records) in a
domain are missing from your server’s database files, you might see the following
messages:
%TCPIP-W-BIND_NOSERVNAM, Server with address 199.85.8.8 is not responding
%TCPIP-E-BIND_NOSERVERS, Default servers are not available
%TCPIP-W-NORECORD, Information not found
-TCPIP-E-BIND_NOSERVERS, Default servers are not available
When the CONVERT/ULTRIX BIND /DOMAIN command creates the .DB files
from the hosts database, it cannot detect the existence of or the names of name
servers in a domain. Therefore, it does not add NS records for the name servers
to the .DB files.
To solve the problem, follow these steps:
1. Stop the BIND server.
2. Manually add NS records for the missing names.
3. Update the start-of-authority (SOA) records by incrementing the serial
number.
4. Restart the BIND server.
5.9.2 Serial Number Mismatch
The serial number mismatch log=xxx, zone=xxx message indicates that the
BIND server was unsuccessful in an attempt to load a particular dynamic update
from the update log file. This can occur because the update is old and no longer
valid. The serial number for the zone has since been incremented and is no
longer in synchronization with the serial number attached to the logged update.
5–48 Configuring and Managing BIND