Re: DLZ with cacher

> The very nature of bind-dlz is that a change
> on the backend data is immediately visible on the frontend.  But if
> you're caching lookups, how would you then make bind actually use that
> changed data?  rndc reload?

rndc flush, rndc flushname, or (in recent releases) rndc flushtree.
Or just using a relatively short TTL.

> That was the main reason I went *to* the DLZ patch, to get away from
> cronjobs and zone rebuild scripts.

There are other reasons for DLZ to be useful, though.

-- 
Evan Hunt -- [email protected]
Internet Systems Consortium, Inc.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/