Received notify, master unreachable (cached)
Matus UHLAR - fantomas
uhlar at fantomas.sk
Fri Jun 17 12:39:32 UTC 2011
On 17.06.11 11:53, Jarosław Świerczyński wrote:
> I have the following problem:
> 1. Slave is trying to contact master for the first time but master in
> zone ./IN: refresh: retry limit for master 10.0.15.1#53 exceeded
> (source 0.0.0.0#0)
> client 10.0.15.1#9947: received notify for zone '.'
> zone ./IN: refresh: skipping zone transfer as master 10.0.15.1#53
> (source 0.0.0.0#0) is unreachable (cached)
> This doesn't seem right. If slave receives the notification from
> master it should know that master is reachable.
If named tells that a master is unreachable, it means that it has tried to
reach the master without success, so the master is unreachable. It's not
about "knowing" master is reachable.
The whole fact that master sent a notify to slave does NOT mean that the
master is reachable from the slave, it only means that slave is reachable
from the master.
> Is this a bug or a configuration problem? Please help. Thank you.
It's apparently configuration problem.
Either the slave tries to reach the master using wrong source IP address
(0.0.0.0#0 means it leaves this to system) or the master does not allow
traffic from slave (e.g. firewall).
try watching network flow between slave and master (capturing packets
to/from master on the slave and vice versa).
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Chernobyl was an Windows 95 beta test site.
More information about the bind-users