BIND8.2.5 logging - underscores invalid

[lauren]

You can put the check-names ignore directive on just that customer's
zone rather than in the global options, ex.

zone "gototal.com" in {
   type slave;
   masters { 192.168.0.3; };
   file "db.gototal.com";
   check-names ignore;
};

that way you will not get the error messages from the offending AD
zone but you should still get them for your other zones.

hope that helps... l




David Nedved <dnedved at nuvox.net> wrote in message news:<a1fic9$lko at pub3.rc.vix.com>...
> Hi All,
> 
> I'm in the process of cleaning up logging on our bind 8.2.5 cluster.
> My eventual goal is that there be nothing in the log file other than
> server reloads and errors.  I'm finding myself constantly frustrated
> that bind seems to lump things together in the same facility and
> error level where I want to see one kind of message and not another.
> 
> My current issue is with lines such as:
> 
> 08-Jan-2002 07:54:32.080 default: warning: owner name "gc._msdcs.gototal.com" IN (secondary) is invalid - proceeding anyway
> 
> I know that underscores are illegal in domain names per RFC.  I know
> that and I like that.  Tell that to M$ though.  Every time we have
> to be secondary for a customer's zones that include M$ active
> directory nonsense, it seems to fill a zone full of names including
> underscores.  Is there an easy way to tell bind 8.2.5 that I don't
> want to be warned every time I reload a zone from a M$ box, but
> still get default:info logging?
> 
> After tackling this one I'll probably have more questions about this
> sort of thing... I'm trying to make it so that I can tail -f the
> named.log on my terminal, and if I see scrollage I jump.  Right now
> I'm jumping constantly for nonsense.  I'd rather not make config
> changes than source code changes so that future upgrades go easier.
> 
> And no, bind 9 is not an option.  Tried it and it didn't work.
> 
> Thanks in advance to anyone who can assist.  Any pointers to more
> in-depth documentation than the ARM specifically with respect to
> logging configuration would also be useful.
> 
> David
> -- 
>    __   __   __ _ __ __      __  __ ____ __   __ _ ____ __
>   /  | /, | / / // //  |    /  |/ // __//  | / / // __//  |
>  / / //   // / // // / /   / , ' // _/ / / // / // _/ / / /
> /___//_/_/ |__//_//___/   /_/|__//___//___/ |__//___//___/
> 
> Unix Systems Engineer              VOICE: +1 864 331 8181
> NuVox Communications, Inc.         FAX:   +1 864 331 1466
> 301 North Main Street, Ste 5000    EMAIL: dnedved at nuvox.net
> Greenville, SC  29601   USA        PAGER: pagenedved at nuvox.net
> 
> -- Attached file included as plaintext by Ecartis --
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iEYEARECAAYFAjw7S3MACgkQNcFAmurdA+N/vACePPEkAcpGFdUqhZ1qjaoYhpXD
> 7EYAniReSeyibMIqNYbMh3TZ6f6oevHf
> =JzcK
> -----END PGP SIGNATURE-----