130 lines
8.2 KiB
HTML
130 lines
8.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Logging Domain Name System server messages" />
|
||
|
|
<meta name="abstract" content="Domain Name System (DNS) provides numerous logging options that can be adjusted when you are trying to find the source of a problem. Logging provides flexibility by offering various severity levels, message categories, and output files so that you can fine-tune logging to help you find problems." />
|
||
|
|
<meta name="description" content="Domain Name System (DNS) provides numerous logging options that can be adjusted when you are trying to find the source of a problem. Logging provides flexibility by offering various severity levels, message categories, and output files so that you can fine-tune logging to help you find problems." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakktroubleshooting.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakktroubleshooting.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakklogging" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Logging Domain Name System server messages</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakklogging"><a name="rzakklogging"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Logging Domain Name System server messages</h1>
|
||
|
|
<div><p>Domain Name System (DNS) provides numerous logging options that
|
||
|
|
can be adjusted when you are trying to find the source of a problem. Logging
|
||
|
|
provides flexibility by offering various severity levels, message categories,
|
||
|
|
and output files so that you can fine-tune logging to help you find problems.</p>
|
||
|
|
<p>BIND 8 offers several new logging options. You can specify what types of
|
||
|
|
messages are logged, where each message type is sent, and what severity of
|
||
|
|
each message type to log. In general, the default logging settings are suitable,
|
||
|
|
but if you want to change them, it is recommended that you refer to other
|
||
|
|
sources of BIND 8 documentation for information about logging.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Logging channels</h4><p>The DNS server can log messages
|
||
|
|
to different output channels. Channels specify where logging data is sent.
|
||
|
|
You can select the following channel types:</p>
|
||
|
|
<ul><li><span class="uicontrol">File channels</span> <p>Messages logged to file channels
|
||
|
|
are sent to a file. The default file channels are as400_debug and as400_QPRINT.
|
||
|
|
By default, debug messages are logged to the as400_debug channel, which is
|
||
|
|
the NAMED.RUN file, but you can specify to send other message categories to
|
||
|
|
this file as well. Message categories logged to as400_QPRINT are sent to a
|
||
|
|
QPRINT spool file for user profile QTCP. You can create your own file channels
|
||
|
|
in addition to the default channels provided.</p>
|
||
|
|
</li>
|
||
|
|
<li><span class="uicontrol">Syslog channels</span><p> Messages logged to this channel
|
||
|
|
are sent to the servers job log. The default syslog channel is as400_joblog.
|
||
|
|
Logging messages routed to this channel are sent to the joblog of the DNS
|
||
|
|
server instance.</p>
|
||
|
|
</li>
|
||
|
|
<li><span class="uicontrol">Null channels</span><p>All messages logged to the null
|
||
|
|
channel will be discarded. The default null channel is as400_null. You can
|
||
|
|
route categories to the null channel if you do not want the messages to appear
|
||
|
|
in any log file.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Message categories</h4><p>Messages are grouped into categories.
|
||
|
|
You can specify what message categories should be logged to each channel.
|
||
|
|
There are many categories, including:</p>
|
||
|
|
<ul><li>config: Configuration file processing</li>
|
||
|
|
<li>db: Database operations</li>
|
||
|
|
<li>queries: Generates a short log message for every query the server receives</li>
|
||
|
|
<li>lame-servers: Detection of bad delegations</li>
|
||
|
|
<li>update: Dynamic updates</li>
|
||
|
|
<li>xfer-in: Zone transfers the server is receiving</li>
|
||
|
|
<li>xfer-out: Zone transfers the server is sending</li>
|
||
|
|
</ul>
|
||
|
|
<p>Log files can become large and they should be deleted on a regular
|
||
|
|
basis. All DNS server log file contents are cleared when the DNS server is
|
||
|
|
stopped and started.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Message severity</h4><p>Channels allow you to filter by
|
||
|
|
message severity. For each channel, you can specify the severity level for
|
||
|
|
which messages are logged. The following severity levels are available:</p>
|
||
|
|
<ul><li>Critical</li>
|
||
|
|
<li>Error</li>
|
||
|
|
<li>Warning</li>
|
||
|
|
<li>Notice</li>
|
||
|
|
<li>Info</li>
|
||
|
|
<li>Debug (specify debug level 0-11)</li>
|
||
|
|
<li>Dynamic (inherit the server startup debug level)</li>
|
||
|
|
</ul>
|
||
|
|
<p>All messages of the severity you select and any levels above it in
|
||
|
|
the list are logged. For example, if you select Warning, the channel logs
|
||
|
|
Warning, Error, and Critical messages. If you select Debug level, you can
|
||
|
|
specify a value from 0 to 11 for which you want debug messages to be logged.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Change logging settings</h4><p>To access logging options,
|
||
|
|
follow these steps:</p>
|
||
|
|
<ol><li>In iSeries™ Navigator,
|
||
|
|
expand <span class="menucascade"><span class="uicontrol">your iSeries server</span> > <span class="uicontrol">Network</span> > <span class="uicontrol">Servers</span> > <span class="uicontrol">DNS</span></span>.</li>
|
||
|
|
<li>In the right pane, right-click <span class="uicontrol">your DNS server</span> and
|
||
|
|
select <span class="uicontrol">Configuration</span>.</li>
|
||
|
|
<li>In the DNS configuration window, right-click <span class="uicontrol">DNS server</span> and
|
||
|
|
select <span class="uicontrol">Properties</span>.</li>
|
||
|
|
<li>In the Server Properties window, select the <span class="uicontrol">Channels</span> tab
|
||
|
|
to create new file channels or properties of a channel, such as the severity
|
||
|
|
of messages logged to each channel.</li>
|
||
|
|
<li>In the Server Properties window, select the <span class="uicontrol">Logging</span> tab
|
||
|
|
to specify which message categories are logged to each channel.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Troubleshoot tip</h4><p>The as400_joblog channel default
|
||
|
|
severity level is set to Error. This setting is used to reduce the volume
|
||
|
|
of informational and warning messages, which can otherwise degrade performance.
|
||
|
|
If you are experiencing problems but the joblog is not indicating the source
|
||
|
|
of the problem, you might need to change the severity level. Follow the procedure
|
||
|
|
above to access the Channels page and change the severity level for the as400_joblog
|
||
|
|
channel to Warning, Notice, or Info so you can view more logging data. After
|
||
|
|
you have resolved the problem, reset the severity level to Error to reduce
|
||
|
|
the number of messages in the joblog.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakktroubleshooting.htm" title="This topic explains Domain Name System (DNS) logging and debugging settings that can help you resolve problems with your DNS server.">Troubleshoot Domain Name System</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakktroubleshooting.htm" title="This topic explains Domain Name System (DNS) logging and debugging settings that can help you resolve problems with your DNS server.">Troubleshoot Domain Name System</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|