bind generating db-* files

Chris Thompson cet1 at hermes.cam.ac.uk
Thu Nov 8 21:47:55 UTC 2007


On Nov 8 2007, Mark Andrews wrote:

[...]
>	I repeat.  The reason *will* be in the logs.  Named only
>	renames the master file when it has detected a error.  The
>	error and that it is renaming the file are logged.

Like it or not, many people running BIND will not be seeing messages
logged at severity INFO, either because they are being suppressed at
the named.conf logging statement level, or because they are being sent
to syslog and suppressed at the syslog.conf level.

Wouldn't a somewhat higher severity be appropriate for these messages,
anyway? I would have thought they deserved at least WARNING.

-- 
Chris Thompson
Email: cet1 at cam.ac.uk



More information about the bind-users mailing list