Information Technology Reference
In-Depth Information
attempt to contact any other DNS servers, including forwarders, to resolve a query. For exam-
ple, you might want to disable recursion when you have a public DNS server containing
resource records for your publicly available servers (Web, e-mail, and so forth). The public
DNS server is necessary to resolve iterative requests from other DNS servers for your public
domain, but you don't want unauthorized Internet users using your DNS server to field recur-
sive client requests.
When DNS is installed, a new event log is created to record informational, error, and warning
events generated by the DNS server. You can configure which event types should be logged in the
Event Logging tab of the server's Properties dialog box (shown in Figure 9-21). Events you're
likely to find in the DNS Server log include zone serial number (referred to as version number in
the DNS Server log) changes, zone transfer requests, and DNS server startup and shutdown
events. The event log can help you diagnose problems, such as when an error causes the server
to stop or keeps it from starting or when communication between servers for replication or zone
transfers has failed. When DNS problems are evident and can't be traced easily to misconfigu-
ration, the event log is the first place to look.
9
Figure 9-21
The Event Logging tab
When serious DNS debugging is warranted, you can enable debug logging in the server's
Properties dialog box. Debug logging records selected packets coming from and going to the
DNS server in a text file. Figure 9-22 shows the packet-capturing options for debug logging.
Search WWH ::
Custom Search