Novell NETWARE 6-DOCUMENTATION Manual page 1701

Solution—Enter the correct domain name or name server address in the
hosts's resolv.cfg file (or equivalent).
Problem—Hosts cannot access an entire external domain.
Cause 1—The root name server information is invalid; therefore, the root
servers are unreachable. For non-eDirectory systems running DNS,
changes to this information are not automatically propagated through a
domain; you must enter the changes manually.
Solution 1—Verify that the IP addresses of the root name servers
configured in the RootServerInfo zone are correct. The most recent
update of root name server information is available through FTP at ftp://
rzs.internic.net/domain/named/root.
Cause 2—The hostname or IP address was not resolved because the
delegation to the zone is incorrect.
Solution 2—Configure the correct hostname or IP address information
for the zone in eDirectory.
Cause 3—The hostname or IP address was resolved to the wrong value.
Solution 3—Change the hostname or IP address information for the zone
to the correct value in eDirectory.
Cause 4—The name server information of the primary name server of the
domain is incorrect or missing in the root name servers.
Solution 4—Verify that the domain is properly registered with the
INTERNIC, the organization that configures the name server information
of the domain.
Cause 5—The name server for the domain is down or is unreachable.
Solution 5—Use PING to locate the connectivity problem. If the problem
exists in your domain, make the necessary repairs to restore connectivity.
Cause 6—The root name server for the domain is down or is unreachable.
Solution 6—Use PING to locate the connectivity problem. If the problem
exists in your domain, make the necessary repairs to restore connectivity.
Cause 7—You do not have sufficient rights to access the zone.
Solution 7—Contact the network administrator for the zone and obtain
sufficient rights to access the zone.
Problem: After you create or modify a Resource Record object, the
change is not reflected in the server cache and the zone transfer fails.
Troubleshooting 127