Slave with IP-Alias doesn't load zone data

[Kevin Darcy]

Dorothee Schweizer wrote:

> Hi,
>
> I have some problems with setting up a bind 9.2.1 Slave Server on a
> Linux 2.4.18 System which has configured an IP-Alias.
> If I try to start the named with the IP-Alias active, zone data files
> are not
> transfered from the master and the following message appears in the
> syslog.
> If I start the named with IP-Alias not active, things work fine, even
> queries
> are answered if I activate the IP-Alias afterwards (of course this makes
> no
> sense, I did it just to test).
> So it seems, the problem is the IP-Alias, but I have no idea why.
> I already asked my Computer Center which is running the Master, but they
> also
> have no idea.
>
> Many Thanks for any Idea,
>
> Doro
> ------------------------------------------------------------------------------
>
> Sep 26 10:36:07 node1 named[4640]: starting BIND 9.2.1
> Sep 26 10:36:07 node1 named[4640]: using 1 CPU
> Sep 26 10:36:07 node1 named[4640]: loading configuration from
> '/etc/named-bind9/named.conf'
> Sep 26 10:36:07 node1 named[4640]: no IPv6 interfaces found
> Sep 26 10:36:07 node1 named[4640]: listening on IPv4 interface eth0,
> XXX.XXX.XXX.XX1#53
> Sep 26 10:36:07 node1 named[4640]: listening on IPv4 interface eth0:1,
> XXX.XXX.XXX.XX2#53
> Sep 26 10:36:07 node1 named[4640]: couldn't add command channel
> 127.0.0.1#953: file not found
> Sep 26 10:36:07 node1 named[4640]: zone 0.0.127.in-addr.arpa/IN: loaded
> serial 42
> Sep 26 10:36:07 node1 named[4640]: zone localhost/IN: loaded serial 42
> Sep 26 10:36:07 node1 named[4640]: running
> Sep 26 10:36:22 node1 named[4640]: zone zzzzz.zzzzzz.zz/IN: refresh:
> failure trying master YYY.YYY.YYY.YYY#53: timed out
> Sep 26 10:36:22 node1 named[4640]: zone XXX.XXX.IN-ADDR.ARPA/IN:
> refresh: failure trying master 129.69.1.28#53: timed out
> Sep 26 10:36:37 node1 named[4640]: zone zzzzz.zzzzzz.zz/IN: refresh:
> failure trying master YYY.YYY.YYY.YYY#53: timed out
> Sep 26 10:36:37 node1 named[4640]: zone XXX.XXX.IN-ADDR.ARPA/IN:
> refresh: failure trying master 129.69.1.28#53: timed out

Since it works without the IP alias, I wouldn't think this was a problem with
your nameserver configuration, but rather some sort of networking problem. When
you're having this problem, trying pinging the master from the slave, or
telnet'ing or FTP'ing. I think you'll find that you have no connectivity to the
master, and named is just a victim of this larger problem...


- Kevin