Date: Wed, 02 Aug 2006 11:21:30 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Edda Hochstrate <eh@netuse.de> Cc: freebsd-isp@freebsd.org, Brian Candler <B.Candler@pobox.com> Subject: Re: Bind9: rndc reload doesn't work for slave servers Message-ID: <44D0ED2A.4070204@FreeBSD.org> In-Reply-To: <44CF51D6.7060406@netuse.de> References: <44CE2043.1040308@netuse.de> <44CE5875.9050509@FreeBSD.org> <44CF3B00.2090106@netuse.de> <20060801124403.GA87804@uk.tiscali.com> <44CF51D6.7060406@netuse.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Edda Hochstrate wrote:
> In our opinion as an ISP the refresh time is for the world of resolvers.
> Authoritative nameservers (especially slaves serving hidden primaries)
> should be as close as possible to the primary.
I'm not sure what you mean by this, but Brian was right. The refresh number
in the SOA tells slave servers how often to poll the master(s) for updates,
servers that query the authoritative servers (resolvers) don't care about
that number.
Your best bet would be to ask your customer to drop the refresh period to
something like 15 minutes, which should be more than adequate.
hth,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D0ED2A.4070204>