Uwe Thiem wrote:
On Wednesday 09 April 2008, 7v5w7go9ub0o wrote:
Ralf Stephan wrote:
Hello,
I'm fed up with waiting for ever the same name requests from my
browser (and open servers don't cut it either): which DNS cache
or caching DNS for simple local installation would you recommend?
consider maradns <http://www.maradns.org/changelog.html>
- It is a recursive dns client/server (and authoritative server if
desired), described in Portage as "Proxy DNS server with permanent
caching>.
Wiht permanent caching?
I don't know. I never found a reference to it in the documentation. I
quoted portage because I thought it might make sense to others.
I'd *guess* that it means that it'll keep long-TTL records beyond a
restart - i.e. it does not flush the cache at start up.
If it really does this, not honouring TTLs,
it's crap. That said, I actually don't know whether they mean
permanent when they say permanent. ;-)
"When MaraDNS' recursive resolver receives a "host not there" reply,
instead of using the SOA minimum of the "host not there" reply as the
TTL (Look at RFC1034 ยง4.3.4), MaraDNS uses the TTL of the SOA reply.
MaraDNS keeps referral NS records in the cache for one day instead of
the TTL specified by the remote server."
"MaraDNS recursive resolver treats any TTL shorter than min_ttl seconds
(min_ttl_cname seconds when the record is a CNAME record) as if the TTL
in question was min_ttl (or min_ttl_cname) seconds long when determining
when to expire a record from MaraDNS' cache.
TTLs which are shorter than 20 seconds long are given a TTL of 20
seconds; TTLs which are more than 63072000 (2 years) long are given a
TTL of 2 years."
HTH
--
gentoo-user@lists.gentoo.org mailing list
