[101774] in North American Network Operators' Group

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

Re: v6 gluelessness

daemon@ATHENA.MIT.EDU (Jeroen Massar)
Fri Jan 18 05:30:56 2008

Date: Fri, 18 Jan 2008 11:29:30 +0100
From: Jeroen Massar <jeroen@unfix.org>
To: Randy Bush <randy@psg.com>
CC: North American Network Operators Group <nanog@merit.edu>
In-Reply-To: <47904C6E.4090806@psg.com>
Errors-To: owner-nanog@merit.edu


This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC73CD2A22B9381B8C283D39C
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable

Randy Bush wrote:
>=20
> for those of us who are trying to provide dual stack services, how the =

> heck do we get v6 glue added to the gtlds?  specifically, i want to add=
=20
> v6 glue for psg.com and rip.psg.com in the com zone.
>=20
> similarly for the root, as rip.psg.com serves some tlds.

Depends on your registrar. As one of the few ones enom.com can add AAAA=20
glue for at least .com and probably some others.

And NetworkSolutions & Joker.com don't even know what 'glue' means, they =

think that you want to use their managed DNS services and put AAAA's in=20
there.

Then again NSI doesn't even get the part right that there are people who =

do not have a phonenumber starting with +1, let alone that some people=20
don't have a fax, thus nicely pushing invalid information into whois.

Some people claim that if you can get through the hoops of the=20
phonesystem at NSI that they can manually add them though.

I've added a little list here:
   http://www.sixxs.net/faq/dns/?faq=3Dipv6glue
Updates and anecdotes of course are welcome :)

Greets,
  Jeroen


--------------enigC73CD2A22B9381B8C283D39C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHkH+KKaooUjM+fCMRAohVAKCCaC+4PfGOEq1dy3IpXX598pVzWQCfVblV
iVKaOf8pRJYeWqIgLCPbnOI=
=I9gL
-----END PGP SIGNATURE-----

--------------enigC73CD2A22B9381B8C283D39C--


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