From: Eric Malkowski <eric@bvwireless.net>
To: buildroot@busybox.net
Subject: [Buildroot] BIND 9.5.1 startup fails w/ IPv6 disabled - PATCH to fix built-in root hints
Date: Tue, 11 Aug 2009 13:54:40 -0400 [thread overview]
Message-ID: <4A81B060.2030902@bvwireless.net> (raw)
Hi all-
When you guys went to BIND 9.5.1_P2 and P3 for kaminsky and dynamic
update DoS fixes, the ISC folks added compiled-in root hints that get
loaded before any other zones (including user specified root hints) and
when IPv6 is disabled via buildroot option (my setup is this way), BIND
will fail to start complaining that the IPv6 AAAA addresses in the built
in root hints are invalid. The error is right after the server outputs
"setting up root hints" and it complains "2001:503:BA3E::2:30 bad IPv6
address"
My solution is attached as a patch against BIND 9.5.1_P3 that simply
puts #ifdef WANT_IPV6 around the AAAA addrs in the built in table and
now bind starts fine and appears to work fine on an IPv4 only buildroot
setup.
It's up to you guys if you want to commit the patch to git. I'm
attaching w/ my Thunderbird e-mail client, hopefully it won't botch the
patch, if so let me know what other ways I can submit the patch.
Thanks -- and hope this helps someone out, I spent too many hours trying
to figure this one out and wanted to at least report it somewhere in
case someone else is googling like mad trying to find an answer.
-Eric Malkowski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bind-fix-ipv6-hints.patch
Type: text/x-patch
Size: 1907 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090811/7f355aca/attachment.bin>
next reply other threads:[~2009-08-11 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 17:54 Eric Malkowski [this message]
2009-09-05 19:16 ` [Buildroot] BIND 9.5.1 startup fails w/ IPv6 disabled - PATCH to fix built-in root hints Peter Korsgaard
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=4A81B060.2030902@bvwireless.net \
--to=eric@bvwireless.net \
--cc=buildroot@busybox.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