update caching nameserver immediately

[Ladislav Vobr]

u can use nsupdate + dnsnotify on your authoritative servers to speed
the master-slave zone transfers, this is provided your authoritative
servers are also recursive and serves as default nameservers for your
clients .

in case you are going to split them, i don't see easy solution, apart
from lowering the ttls, or bind 9.3 flush as you mentioned.

u can make the recursive server stealth slave and use dnsnotify to
update it's "hidden secondary zone"

Ladislav

Will Yardley wrote:
> We have been using our authoritative nameservers for internal resolution
> for quite some time. This is obviously not an ideal way of doing things,
> but I've been working on gradually changing this for quite some time.
> 
> Our system makes certain assumptions based on the assumption that
> internal hosts will resolve names based on a response from one of the
> authoritative servers. There are certain cases where we shift something
> internally, and it's important that the internal resolution updates
> almost instantly.
> 
> It looks like BIND 2.3 will support "flushname", which may do what we
> want (flush an individual zone from the cache). Is there any way,
> however, to use the NOTIFY mechanism to flush a zone from the cache
> automatically?
> 
> Any other way to make sure that zones are kept in sync with the
> authoritative servers *without* configuring all of the zones as slaves
> and without setting ridiculously low TTLs?
>