Diagnosing problems with unresponsive name servers

Use the statistics supplied in message EZZ9310I to determine the severity of the problem that the resolver is reporting. For example, if the unresponsive name server is the primary server for the network, and it is failing to respond to over half of a large number of queries that are directed to it, that situation might be more serious than a secondary name server that is not responding to 25% of a small number of queries. You can also use the statistics that are displayed when message EZZ9309I is issued to determine whether the name server is fully responsive again, is likely to become unresponsive again because the failure rate is still close to the threshold value, or is just not being used in your environment.

Guideline: The resolver does not require that there be a certain number of failed queries to a particular name server before it declares that server to be unresponsive. For example, if only one query is received by a particular name server during a monitoring interval, and that query fails to obtain a response, then the resolver considers that name server to be 100% unresponsive.