HP-UX IP Address and Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3
— Problem 5, Network Connectivity
— Problem 10, /etc/hosts or NIS contains Incorrect Data
• Names in the local and remote domains are looked up successfully. However, other servers
not in your domain cannot look up names within your domain. Check the following:
— Problem 7, Incorrect Delegation of Subdomain
Name Server Problems
This section explains the problems that may cause the symptoms listed above, and suggests ways
to solve the problems.
1. Incorrect parameters supplied to hosts_to_named.
Check the domain data files to be sure they contain records for the hosts in your domain. If
localhost is the only host listed, you may have supplied incorrect domain names or
network numbers to hosts_to_named.
2. Syntax error in the named.conf file or a data file.
• syslogd
Syntax error messages are logged indicating the file name and line number.
• Name server debugging output
Start the name server at debug level 1. Look for syntax error messages in
/var/tmp/named.run indicating the file name and line number.
• ping hostname
If ping indicates that the host is unknown and the local name server should be
authoritative for that name, the syntax error is probably in the file that maps host names
to Internet addresses, db.domain.
3. Missing cache information about the root servers. Without information about the root servers,
names outside of the local domain cannot be looked up because the local server relies on
the root servers to direct it to servers for other domains.
• syslogd
Queries for names outside of the local domain cause syslogd to log the following
message: No root name servers for class 1. (Class 1 is the IN class.)
• nslookup
nslookup may fail to look up the local host’s name on startup and give a servfail
message. To verify root server information, execute the following:
$ nslookup
> set type=NS
> .
92 Configuring and Administering the BIND Name Service