Issues with rndc not picking up zone changes

[Barry Margolin]

In article <da1d0k$15f6$1 at sf1.isc.org>, Kvetch <kvetch at gmail.com> 
wrote:

> We are using BIND 9.3.0 for our DNS servers and are using a DNS management 
> program called ProBind to handle updates and changes to the zone files.
> We are experiencing intermittent problems with BIND not loading changes to 
> the zone files after the Probind program runs the "rndc -c rndc.conf reload" 
> command via ssh. I can see in the BIND logs where ProBind pushes out the new 
> named.conf and I can verify that the new versions of the zone files are 
> being put on the DNS servers. In the named logs, I see:
> general: loading configuration from '/etc/named.conf'
> 
> However, I don't always get the zone file reload in the log file similar to:
> general: zone blahblah.org/IN <http://blahblah.org/IN>: loaded serial 
> 2005062907
> notify: zone blahblah.org/IN <http://blahblah.org/IN>: sending notifies 
> (serial 2005062907)
> 
> This issue only happens intermittently. Is this a known issue with rndc 
> reload? Has anyone else seen this behavior?
> I know we can always stop and restart the named service to force a total 
> zone reload, but I'd rather use the rndc reload since it only affects the 
> files that are updated (when it works properly...).

The only thing that comes to mind is that your mechanism of pushing out 
the updated zone files is somehow not updating the modification times of 
the files.  Reload uses the file modification time to determine if the 
zone file has changed and needs to be reloaded.

Could you be getting out of sync, sending the reload command before all 
the file transfers have completed?

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***