help with notify-source
Barry Margolin
barmar at alum.mit.edu
Wed Mar 26 04:50:18 UTC 2008
In article <fsc8i4$25ee$1 at sf1.isc.org>, tony z <tzucc at yahoo.com> wrote:
> hi Barry,
> yes I did check logs... I even turned on debug logging at level 50... no
> errors on startup... no errors at times when NOTIFYs were going out on the
> wrong IP address (in other words not the IP configured in notify-source). And
> yes, I am 100% sure I was editing the named.conf that named was using... I
> just checked now, and there is no other named.conf, no chroot directory,
> etc...
And if you put a syntax error in the file, does it log an error?
Something MUST be causing it to ignore these lines in the file.
> Again, perhaps the issue with BIND and IP's assigned to ethernet alias. BIND
> kept going to eth1 first, then rotating around all my other IPs on the
> eth0:[0-3] .... totally ignoring my notify-source. I did post my
> named.conf... was how I used notify-source ok?
If you used it wrong you would have gotten a syntax error in the log.
But it's behaving as if you didn't use it at all. Alias IPs are fine,
that's an expected use of this option.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list