Alan Clegg writes:
> Are you able to "dig @139.78.100.1 78.139.IN-ADDR.ARPA axfr" when logged
> into the slave?
No and your diagnosis was spot on.
> It seems that communications between the slave (which we don't know the
> IP address of) and the server at 139.78.100.1 is broken.
Oh, yes!
On 10/26/2010 8:45 AM, Martin McCormick wrote:
> 26-Oct-2010 07:30:46.497 zone 78.139.IN-ADDR.ARPA/IN: refresh:
> skipping zone transfer as master 139.78.100.1#53 (source 0.0.0.0#0) is
> unreachable (cached)
Are you able to "dig @139.78.100.1 78.139.IN-ADDR.ARPA axfr" when logged
into the slave
Ah, the wonderful world of high stakes no-return upgrades!
I turned on a new installation of bind9.7.1 after
running it in slave mode for a few days and:
26-Oct-2010 07:30:46.497 zone 78.139.IN-ADDR.ARPA/IN: refresh:
skipping zone transfer as master 139.78.100.1#53 (source 0.0.0.0#0) is
3 matches
Mail list logo
