From: Justin Whitney <ripple@ripple.be>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] djbdns 1.05-r8 breaks forward-only behaviour of dnscache
Date: Thu, 16 Oct 2003 01:43:34 -0500 [thread overview]
Message-ID: <1066286611.5224.13.camel@localhost> (raw)
Hi,
The round-robin patch included in the djbdns-1.05-r8 ebuild breaks
default dnscache FORWARDONLY behaviour. this means that servers/@ and
env/FORWARDONLY are not honored, and the ns roots are queried for
lookups. The result of the patch is that if you set FORWARDONLY and
servers/@ to a non-root cache, expecting to make efficient use of, say,
your ISP's nameservers, you'll end up doing far more queries than you
intended for any given lookup... on my systems because of latency I was
timing out for a lot of lookups. to test, compile with rr-patch, set
dnscache up to do forward-only (per DJB's docs), and then sniff to see
the root queries I mentioned. recompile without it, and repeat to see
the difference.
bug filed.
--Justin Whitney
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-10-16 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 6:43 Justin Whitney [this message]
2003-10-16 7:17 ` [gentoo-dev] djbdns 1.05-r8 breaks forward-only behaviour of dnscache Andrei Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1066286611.5224.13.camel@localhost \
--to=ripple@ripple.be \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox