problem after upgrading bind.
mark evans
evansmb74 at gmail.com
Tue Oct 9 16:03:03 UTC 2007
Yes, i did run the dig from the slave. i will try the tcpdump. when i
restarted the bind 8.4 on the master the slave seems to have pulled the
zones over because it is no longer showing expired. So i have to wait for
another zone to expired. I will try the tcpdump as soon as i get an expired
zone.
Thanks for you assistance
Mark
On 10/9/07, Niall O'Reilly <Niall.oReilly at ucd.ie> wrote:
>
>
> On 9 Oct 2007, at 16:12, mark evans wrote:
>
> > The only error i see logged about this domain is the expired
> > message, which
> > i get when i start the server. I tried renaming the zone file and and
> > forcing the transfer but the zone file was not created on the slave.
> >
> > we also are not seeing any errors logged on the master.
>
> From what you've explained --
>
> Zone transfer from master works manually using dig;
> Zone transfer from maser doesn't work automatically using named;
> Zone trnsfer request from named seems not to reach the master.
>
> Something is different between the request you generate manually
> and the one which named generates.
>
> Did you run dig on the same system where the slave named is
> running?
> What does your favorite packet-capture utility (tcpdump, for
> example)
> tell you?
>
> /Niall
>
>
>
More information about the bind-users
mailing list