Re: DLZ with cacher
Todd Lyons <[email protected]> Wed, 4 Jul 2012 10:14:27 -0700
| Newsgroups | gmane.network.dns.bind9.dlz |
|---|---|
| Message-ID | <CAFG21ojEiB0FduUm3ZoRaYerCm0iLxEOiGSujfwcbnt0F_g+VA@mail.gmail.com> |
On Tue, Jul 3, 2012 at 11:39 PM, Jorgen Lundman <[email protected]> wrote: > > Our current DLZ+LDAP+BIND is running very well. But something I have been > playing with at the same time, instead of DLZ talking to LDAP for each > QUERY, find a way to use BIND's caching. 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. ...Todd -- The total budget at all receivers for solving senders' problems is $0. If you want them to accept your mail and manage it the way you want, send it the way the spec says to. --John Levine ------------------------------------------------------------------------------ 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/