help with notify-source

[Barry Margolin]

In article <fsc5ru$1v2f$1 at sf1.isc.org>, tony z <tzucc at yahoo.com> wrote:

> hi Mark,
> Oh I did restart named for sure - several times. Not just reload, but 
> restart. And I definitely used addresses
> copied from ifconfig, so that wasn't the issue either (just to make sure I 
> didn't typo).
> named-checkconf reported no errors.  I also scoured iptables for some 
> blocking condition
> that could cause BIND to mess up. Nothing appeared out of order.
> 
> The only thing I can think of, if it is a BIND bug, is that the IP I used for 
> notify-source was
> an IP assigned to an ethernet alias (RHEL5).
> 
> In any case, I wouldn't bet that there isn't some other misconfiguration of 
> mine that is causing this
> but it sure isn't obvious. 

Are you absolutely sure that the config file you were editing is the one 
that named is using?  There have been many occasions when someone has 
edited /etc/named.conf, but their system was actually using 
/etc/named/named.conf, or something like that.

Have you checked your log to see if it's reporting any errors when it 
starts up?

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***