DNS nslint error messages

Paul Schmehl pauls at utdallas.edu
Thu Feb 2 15:02:26 PST 2006


--On Thursday, February 02, 2006 17:54:11 -0500 Brad Gilmer 
<bgilmer at 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 at utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/ir/security/


More information about the freebsd-questions mailing list