[80122] in North American Network Operators' Group
Re: Problems with NS*.worldnic.com
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Tue Apr 26 03:11:55 2005
To: "william(at)elan.net" <william@elan.net>
Cc: Rodney Joffe <rjoffe@centergate.com>, Randy Bush <randy@psg.com>,
nanog@nanog.org
In-Reply-To: Your message of "Mon, 25 Apr 2005 22:19:51 PDT."
<Pine.LNX.4.62.0504252157160.2760@sokol.elan.net>
From: Valdis.Kletnieks@vt.edu
Date: Tue, 26 Apr 2005 03:10:41 -0400
Errors-To: owner-nanog@merit.edu
--==_Exmh_1114499440_3571P
Content-Type: text/plain; charset=us-ascii
On Mon, 25 Apr 2005 22:19:51 PDT, "william(at)elan.net" said:
> Perhaps a solution is to specifically enable ipv6 dns resolution as
> preferable to ipv4 or the other way around. This could perhaps be
> switch in resolv.conf or nsswitch.conf. Something like:
> /etc/resolv.conf
> search example.com
> protocol ipv6 ipv4
At least on my system, there's an 'options inet6' line that makes it look
for AAAA records, and mapping ipv4 into ipv6 addresses if only an A record
is found.
Also note that it doesn't fix the problem that's being seen - I might
be able to contact the nameservers listed in resolv.conf via both IPv4
and IPv6 - the fun starts when my nameserver gets an NS entry that contains
an AAAA record, and the nameserver has enough IPv6 connectivity to think
it's worth a try, but you can't get there from here...
--==_Exmh_1114499440_3571P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQFCbelwcC3lWbTT17ARAvG2AJ4yAzFEhjqMV+kigqqhuR20KdlQ7ACg6zEv
nEfRvG7b4L/ckXOmDMa676Y=
=efGj
-----END PGP SIGNATURE-----
--==_Exmh_1114499440_3571P--
