slave transfer troubleshooting issue

Jakob Bohm egenagwemdimtapsar at jbohm.dk
Sat Oct 10 00:35:20 UTC 2009


On Tue, 06 Oct 2009 12:20:13 -0400, Frank Pikelner <frank.pikelner at netcraftcommunications.com> wrote:
> I have two Debian servers running BIND 9.5.1-p3 (master and slave). I
> have taken the configs from a production environment that work, just
> changed IP addresses. I am having problems sorting out why the slave
> fails to tranfer files from the master. The /var/log/bind/named.log on
> the master shows that all relevant zones have been loaded. When I check
> the /var/log/bind/named.log file the slave is only loading the defaults:
> 
> 06-Oct-2009 12:09:45.358 general: info: zone 0.in-addr.arpa/IN/internal:
> loaded serial 1
> 06-Oct-2009 12:09:45.358 general: info: zone
> 127.in-addr.arpa/IN/internal: loaded serial 1
> 06-Oct-2009 12:09:45.358 general: info: zone
> 255.in-addr.arpa/IN/internal: loaded serial 1
> 06-Oct-2009 12:09:45.362 general: info: zone localhost/IN/internal:
> loaded serial 2
> 06-Oct-2009 12:09:45.362 general: info: zone bind/CH/external-chaos:
> loaded serial 1
> 06-Oct-2009 12:09:45.366 general: notice: running
> 
> 
> My named.conf file has an include statement for named.conf.local. I've
> checked permissions, files and all seems to be okay. I must be missing
> something simple. What is the best way to debug why the slave does not
> seem to attempt a transfer of the additional zones from the master?
> 
> 
> Thank you,
> 
> Frank
> 
> 

The Debian packaged bind differs from the standard bind in one important
detail, which may be the cause of your problems:

Debian bind looks for named.conf and related files in /etc/bind/named.conf,
standard bind looks in /etc/named.conf.

(Sorry for not replying earlier, I don't read this list every day.)


-- 
This message is hastily written, please ignore any unpleasant wordings,
do not consider it a binding commitment, even if its phrasing may
indicate so. Its contents may be deliberately or accidentally untrue.
Trademarks and other things belong to their owners, if any.



More information about the bind-users mailing list