[174526] in North American Network Operators' Group
Re: Bare TLD resolutions
daemon@ATHENA.MIT.EDU (Fred Baker (fred))
Wed Sep 17 18:09:58 2014
X-Original-To: nanog@nanog.org
From: "Fred Baker (fred)" <fred@cisco.com>
To: Jay Ashworth <jra@baylink.com>
Date: Wed, 17 Sep 2014 22:04:07 +0000
In-Reply-To: <18573980.1992.1410970155561.JavaMail.root@benjamin.baylink.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
--Apple-Mail=_FF5BC45B-DD36-479A-9787-06BBC02D601A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
IMHO, since ICANN has created the situation, the ball is in ICANN=92s =
court to say how this works without disrupting name services. Their =
ill-informed hipshot is not our emergency.
On Sep 17, 2014, at 9:09 AM, Jay Ashworth <jra@baylink.com> wrote:
> Pursuant to
>=20
> https://www.icann.org/resources/pages/name-collision-2013-12-06-en)
>=20
> mentioned in the Scotland thread... it seems there are two major =
potential
> points of possible collision:
>=20
> 1) User network uses "fake" TLD which is no longer fake, and local=20
> resolver server blows it
>=20
> 2) User network blows it worse, and tries to resolve a monocomponent =
name
> off non-local servers.
>=20
> The latter would seem to be avoidable by making sure that *DNS =
resolution
> of bare TLDs always returns NXDOMAIN*.
>=20
> Is that a requirement for a TLD?
>=20
> If it isn't, does anyone know of any domains dumb enough to actual=20
> return something for a lookup on the bare TLD?
>=20
> Is there actually *any* good reason why a lookup on a bare TLD =
("com.")
> might return a valid record?
>=20
> And what about Naomi?
>=20
> Cheers,
> -- jra
>=20
> --=20
> Jay R. Ashworth Baylink =
jra@baylink.com
> Designer The Things I Think =
RFC 2100
> Ashworth & Associates http://www.bcp38.info 2000 Land =
Rover DII
> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 =
647 1274
--Apple-Mail=_FF5BC45B-DD36-479A-9787-06BBC02D601A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iD8DBQFUGgVVbjEdbHIsm0MRAox5AKDGneohKGojB18l63Un1cJyd86gKACg+X/J
NfRmkonj0re/Bfczo0eLXq8=
=6n6r
-----END PGP SIGNATURE-----
--Apple-Mail=_FF5BC45B-DD36-479A-9787-06BBC02D601A--
