bind-9.1.0 zone update problem

[Sergey Nikolaev]

Yes, that machine is multihomed and that was a problem. Now I fixed it.
Thanks!

Still, on the master server I get these messages

IXFR version not in journal, falling back to AXFR

Both the master and the secondary are 9.1.0. I even tried provide-ixfr
on the master with no effect.

What is that journal?

Sergey

arnold at theoffice.net wrote:
> 
> Why don't you use the ndc utility that comes with 8.2.2 and higher.
> ndc reconfig will clear out zones no longer served and add zones
> served by it with minimal delay.
> doing ndc reload zonename will just refresh that zone in the BINDS
> DB(memory)
> 
> Do you have a multihomed machine which sends the notify?
> 
> Arnold K.
> 
> On 31 Jan 2001 16:00:05 -0800, in comp.protocols.dns.bind you wrote:
> 
> >
> >Hi,
> >
> >I have just upgraded from bind-8.2.2-P5 to bind-9.1.0 on my master and
> >secondary servers.
> >
> >When I update a zone file (by increasing the serial number) on the
> >master
> >server and HUP the server process, I do see from a log file that it
> >sends
> >a notify to the secondary server, but the secondary server does not seem
> >to receive that notify, and consequently does not update the zone.
> >With bind-8.2.2 it usually updated the secodary server within a minute.
> >
> >What is wrong? Can anybody help please.
> >
> >
> >Sergey
> >
> 
> Voicenet System Administration