From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages] c78835: named: caching the roots has too many dependencies
Date: Mon, 02 Apr 2012 22:02:08 -0700 [thread overview]
Message-ID: <4f7a8450b7628_4fe61508aec53532@sh2.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages
Commit: c78835f26da2e5989cd41a4857e1c23f35603b67
https://github.com/dtaht/ceropackages/commit/c78835f26da2e5989cd41a4857e1c23f35603b67
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-02 (Mon, 02 Apr 2012)
Changed paths:
M net/bind-latest/files/chroot/named/etc/bind/default/other.zones
Log Message:
-----------
named: caching the roots has too many dependencies
While the performance benefit of caching the roots seems good...
on boot, this leads to cascade failures while dnssec is not working.
bind ends up throttling the connections to the roots, or vice versa
and it can take minutes to actually get anywhere, during which time
ntp is kicking the nameserver and vice versa, and sometimes
we never get anywhere.
reply other threads:[~2012-04-03 5:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4f7a8450b7628_4fe61508aec53532@sh2.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@lists.bufferbloat.net \
/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