Configuration of bind8
barmar at bbnplanet.com
Fri Mar 10 22:09:47 UTC 2000
In article <F2413A849CC9D211AC3500805FFE3E970992BF at swan.bcsc.gov.bc.ca>,
Evans, Lorne R ISTA:EX <Lorne.Evans at gems1.gov.bc.ca> wrote:
> After successfully running W2K DDNS as master - I setup BIND
>22.214.171.124P to be the master instead for the W2K zones. I blindly specified
>the W2K defaults for the SOA as per the attached - but get the following
>BIND messages. Given the default TTL for the dynamic W2K SRV records
>appears to be 10 minutes - are there any rules of thumb for determining
>optimal BIND SOA values for the expire, retry, and refresh values? I found
>Jim's recommedation for expire - but - came up empty for retry and refresh?
> Thanks - and - attached....
>master zone "_sites.blah.ca" (IN) loaded (serial 2000030615)
>db._tcp.blah.ca: WARNING SOA expire value is less than 7 days (86400)
>db._tcp.blah.ca: WARNING SOA refresh value is less than 2 * retry (900 < 600
It depends on how quickly you need DNS changes to propagate. If you reduce
the refresh time, slave servers will check for changes on the master more
often. But this also means more load on the masters and slaves, since they
perform these checks more often, and that takes time away from serving
ordinary queries. Unless you're hosting thousands of domains this probably
isn't significant, though.
If all your slave servers support the NOTIFY protocol (BIND 8 and Microsoft
DNS support it) then refresh time isn't too important. When the domain is
changed, the master will notify the slaves, and they'll perform a zone
transfer within a few minutes.
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.
More information about the bind-users