[Pdns-users] ixfr support for slaves with large zones

[Sean Boran]

Hi Kennet,

Thanks for the quick response.
"It sounds like your best bet is to script/cron the update to occur
periodically
instead of every second to manage the I/O."

Yes, that did sound like the best scenario. I wend looking for commandline
options that would allow me to do a zone transfer, on demand from cron.
But I found nothing. I also browsed the source, but didn't see any such
tools.
Have I missed something?

Sean

2009/3/19 Kenneth Marshall <ktm at rice.edu>

> On Thu, Mar 19, 2009 at 03:52:34PM +0100, Sean Boran wrote:
> > Hi,
> >
> > I have a pdns slave to a very large zone (and I do not have
> administrative
> > access to the master server), where the serial changes almost every
> second.
> > This means that the entire zone keeps being sent. The ixfr protocol,
> seems
> > to be the solution in that only the changes to a zone would be
> propagated.
> > http://www.dns.net/dnsrd/rfc/rfc1995.html
> >
> > However, when I search for pdns support for ixfr I dind't much much
> execpt a
> > patch two years ago to answer ixfr queries and force full transfers.
> >
> > So ixfr is not yet supported, is that correct?
> >
> > Thanks in advance,
> >
> > Sean Boran
>
> Sean,
>
> That is correct, IXFR is not supported so pdns falls back to using
> AXFR for the transfer. I had posted a patch to at least allow for
> the DB update process to be optimized a few years ago. This kept
> the DB backend from being overrun by the AXFR updates. It sounds
> like your best bet is to script/cron the update to occur periodically
> instead of every second to manage the I/O. Good luck.
>
> Cheers,
> Ken
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20090320/e6d09e61/attachment-0001.html>