Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 02 Feb 2006 17:00:57 -0600
From:      Paul Schmehl <pauls@utdallas.edu>
To:        Brad Gilmer <bgilmer@gilmer.org>, cswiger@mac.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: DNS nslint error messages
Message-ID:  <F0AA88D201C3CAF48737832A@utd59514.utdallas.edu>
In-Reply-To: <20060202225411.GA31059@gilmer.org>
References:  <20060202225411.GA31059@gilmer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--On Thursday, February 02, 2006 17:54:11 -0500 Brad Gilmer 
<bgilmer@gilmer.org> wrote:
>
> 5) One more newbie comment - be sure to check /var/log/messages for
> errors.  nslint does not catch everything.  If you are pounding away
> making numerous changes, you can quickly check for log error messages by
> entering...
>
># rndc reload
>
> This will cause BIND to re-read the zone files.
>
You can also add this to /etc/rc.conf:

named_flags=" -d 4" (or pick a number you like)

which will start bind with the debug switch on and generate a great deal of 
traffic to your logs.  Or you can do this:

named_flags=" -d 4 -g", and rather than logging the traffic, bind will 
print it to stderr (your screen), and you can watch it as it runs.

Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/ir/security/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F0AA88D201C3CAF48737832A>