Bind 8.2.1 & IXFR

[James Hall-Kenney]

BTW - last time I queried the list about IXFR on 8.2.1, the answer from Mark
@ isc was that it was "broken" in 8.2.1 and not to use it (no specifics -
sorry).  

Once I twigged on the nsupdate requirement, IXFR did work ok in testing -
but don't expect to keep your zone files nicely formatted and commented!

The release notes for 8.2.2 show lots of fixes for 8.2.2 - I haven't seen
any postings on the list from people who had trouble with 8.2.1 but have
found 8.2.2 to fix the probs...

J.


-----Original Message-----
From: Barry Margolin
To: comp-protocols-dns-bind at moderators.uu.net
Sent: 26/10/99 06:32
Subject: Re: Bind 8.2.1 & IXFR

In article <199910251559.KAA04836 at tstdns4.sbc.com>,
Blair Porter  <bp3434 at tstdns4.sbc.com> wrote:
>I am beginning to tinker with IXFR, using Bind 8.2.1.  I have a master
and
>slave server set up to test with.  I put maintain-ixfr-base in the
options
>section of my configuration on both the master & slave.  I put the
ixfr-base
>option in the zone portion of the configuration.  I put the
support-ixfr
>option in the server portion of the configuration.  I also put the
notify yes
>option in the zone portion of the configuration.  I restarted named via
ndc
>on the master and slave.  I then manually updated the zone data on the
master,
>incremented the SOA and did a ndc reload.  The notify worked, but the
transfer
>was AXFR, not IXFR.  What else needs to be done to successfully use
IXFR???

I believe BIND only supports IXFR for domains that are updated using
dynamic update.  If you simply reload a new zone file on the master, it
doesn't perform a "diff" to determine the changes.  But if you use
dynamic
update, it maintains a log of the updates, and IXFR sends those changes.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to
newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the
group.