Re: DLZ with cacher

Todd Lyons wrote:
>
> This question has been asked many times over the course of the years
> of the Bind-DLZ patch.  The answer was always to configure the backend
> (ldap or sql) for optimum caching and leave the bind frontend just a
> parser to construct the appropriate query and return the appropriate
> answer to the querier.  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?  That was the main reason I went *to* the
> DLZ patch, to get away from cronjobs and zone rebuild scripts.

With a TTL of 60, or 600, or whatever short value you can imagine, I would 
be happy if it use that for updates. It sort of already does, with all the 
other non-DLZ named out there that caches lookups.

But anyway, bind has no "proxy" mode where it will keep "aa" flags, and 
ignore norec to forward anyway.

But, it was only 2 line change to hack around that.

Lund

-- 
Jorgen Lundman       | <[email protected]>
Unix Administrator   | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo    | +81 (0)90-5578-8500          (cell)
Japan                | +81 (0)3 -3375-1767          (home)



------------------------------------------------------------------------------
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/