Common Operational Problems - Novell NETWARE 6-DOCUMENTATION Manual

Common Operational Problems

3. Verify consistency between Pointer records in the IN-ADDR.ARPA
domain and other domains.
4. If you change the IP address of a name server, ensure that the parent zone
reflects that change.
5. Verify that you have configured a name server to correctly serve every
zone.
6. Verify that zone transfers are occurring properly. Ensure that the
secondary name server can identify the primary name server.
7. If you cannot access a particular host, verify that PTR records exist. When
you create a zone, always select Yes when prompted to create a
companion zone. If you created a companion zone, verify that the IP
address and hostname are correct.
Internet RFC 1912 provides information about common operational errors
found in both the operation of DNS servers and the data the DNS servers
contain. The following list describes the most common operational errors that
occur.
Problem—Hosts cannot access a particular system. You changed the IP
address for this system recently, but the secondary name server has not yet
been updated.
Cause—The Start of Authority (SOA) record's serial number was not
properly incremented. Without the serial number increment, the
secondary name server does not recognize when a change has been made.
This is usually not a problem with eDirectory
serial number is incremented automatically. With UNIX systems, failure
to increment the serial number is the most common cause of DNS errors.
The secondary server does not automatically test for changes in the SOA
record. Any changes in the SOA record must be accompanied by a change
in the SOA record serial number.
Solution—Do not change the SOA record serial number manually with
eDirectory-based DNS. If the primary server is not eDirectory-based, you
might need to change the serial number manually for the secondary server
to recognize that a change has occurred.
Problem—You cannot access a particular host.
-based DNS because the
TM
Troubleshooting 125