On Wed, 5 Aug 1998, Kevin P. Fleming wrote:
> I agree. I follow the same policy, that the mailhost always has direct,
> fast access to a caching nameserver, so I'd prefer Exim never directly
> cache DNS lookup results at all.
More agreement here. It is bad practice for an application to cache
DNS information unless it is going to adhere to the TTL data as a name
server would. The failure to do this invariably leads to difficult to
diagnose problems in periods of DNS transition.
All the necessary code for DNS caching is already done, in bind. Run
a caching name server locally as others have suggested and you get the
best of both worlds, performance and compliance.
--
Paul Phillips | Something that flies that doesn't have an engine -
Shop Herder | A bicycle with wings
<paulp@???> | -- heard on Family Feud
+1 206 447 1595 |--------* http://www.go2net.com/people/paulp/ *--------
--
*** Exim information can be found at
http://www.exim.org/ ***
