[bind10-dev] guide comments

JINMEI Tatuya / 神明達哉 jinmei at isc.org
Wed Nov 14 17:44:54 UTC 2012


At Wed, 14 Nov 2012 11:25:37 -0600 (CST),
"Jeremy C. Reed" <jreed at isc.org> wrote:
> 
> 4) the guide mentions about limitations in IXFR twice. Search xml for 
> "1279" in a comment. The #1279 ticket is now closed. Is the AXFR default 
> still due to IXFR limitation(s)?

In my understanding yes, but the doc is a bit stale.  The "One
reason..." block should now read, e.g.:

      <note><simpara>
      The main reason why IXFR is disabled by default in the current
      release is because it does not use AXFR even
      if it has no knowledge about the zone (like at the very first
      time the secondary server is set up).  IXFR requires the
      "current version" of the zone, so obviously it doesn't work
      in this situation and AXFR is the only workable choice.
      The current release of <command>b10-xfrin</command> does not
      make this selection automatically.
      These features will be implemented in a near future
      version, at which point we will enable IXFR by default.
      </simpara></note>

We might also remove the famous phrase of "near future".  It's vague
and meaningless, and in its usual sense often not true.

---
JINMEI, Tatuya


More information about the bind10-dev mailing list