[bind10-dev] Is AXFR/IXFR needed for DB-based (especially large) zones?

Michal 'vorner' Vaner michal.vaner at nic.cz
Mon Jun 13 08:26:34 UTC 2011


Hello

On Fri, Jun 10, 2011 at 05:32:10PM -0700, JINMEI Tatuya / 神明達哉 wrote:
> Looking at other implementations, BIND (9) DLZ insists that it's a bad
> practice: http://bind-dlz.sourceforge.net/worst_practices.html and
> database replication should be used instead.
> 
> DLZ supports AXFR, too, but if I understand the code correctly, it
> simply takes the in-memory approach, so it's not scalable for larger
> zones.  PowerDNS's AXFR support basically seems to be the same (I
> don't know what's the recommended practice for server synchronization
> when using PowerDNS).

Well, the in-memory has a disadvantage that you need to load it manually and it
takes RAM. We could let the DB backend do something like this for us with stuff
like copy-on-write versioning. For example, this suggests that mysql is capable
of doing so:
http://dev.mysql.com/doc/refman/5.0/en/internal-locking.html
which I expect happens on disk.

Anyway, the 10-minutes lock might not be that big problem maybe, if it was a
hidden master, then just the write operations would wait for the 10 minutes,
happen at once and then another sends can happen.

I don't know if it's what you ask for, but anyway.

With regards

-- 
Wait few minutes before opening this email. The temperature difference 
could lead to vapour condensation.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20110613/7a378986/attachment.bin>


More information about the bind10-dev mailing list