[157371] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Please, talk me down.

daemon@ATHENA.MIT.EDU (JP Viljoen)
Wed Oct 17 01:32:07 2012

From: JP Viljoen <froztbyte@froztbyte.net>
In-Reply-To: <2801F5F8-B8E2-4A9F-9A89-02D7783CCDA7@josephholsten.com>
Date: Wed, 17 Oct 2012 07:25:58 +0200
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 17 Oct 2012, at 5:35 AM, Joseph Anthony Pasquale Holsten =
<joseph@josephholsten.com> wrote:
> I want to like IPv6. I do. But I'm seriously considering turning off =
IPv6 support from our servers.
>=20
> First off, I'm using djbdns internally and it doesn't support AAAA =
records. So we really aren't using it internally.
>=20
> But today I noticed that we have a lot of traffic to our DNS cache, =
and started to investigate. Turns out that every DNS request would start =
with one for the AAAA record. Ah, no luck. Maybe you forgot the search =
domain? Let's retry that DNS request with that tacked on. Failed again? =
Meanwhile, lets simultaneously try for the AA record then. Repeat.

++ on what everyone else has said about this being a problem with the =
way you run your DNS infrastructure, instead of an actual IPv6 problem.

Without reasons listed for why you use djbdns, I can't really adequately =
comment, but: on our net we're using unbound as caching DNS servers with =
pretty good success, and pdns with dynamic backends (the backends are =
custom in-house stuff) as our authoritative DNS. Short of issues now and =
then with the backends, it works pretty well.

-J=


home help back first fref pref prev next nref lref last post