[174517] in North American Network Operators' Group
Re: Bare TLD resolutions
daemon@ATHENA.MIT.EDU (Jay Ashworth)
Wed Sep 17 16:58:05 2014
X-Original-To: nanog@nanog.org
Date: Wed, 17 Sep 2014 16:57:52 -0400 (EDT)
From: Jay Ashworth <jra@baylink.com>
To: nanog@nanog.org
In-Reply-To: <20140917204640.37641.qmail@joyce.lan>
Errors-To: nanog-bounces@nanog.org
----- Original Message -----
> From: "John Levine" <johnl@iecc.com>
> >The latter would seem to be avoidable by making sure that *DNS resolution
> >of bare TLDs always returns NXDOMAIN*.
> >
> >Is that a requirement for a TLD?
>
> No. In fact, a TLD lookup that returned NXDOMAIN would be utterly
> broken since that would mean the TLD had no SOA, no NS, and no
> subdomains. Perhaps you're confusing it with NOERROR.
No, I was confusing you for someone who understood -- as everyone else
here seems to have -- that I meant "querying for an A, AAAA, or MX
record".
> >If it isn't, does anyone know of any domains dumb enough to actual
> >return something for a lookup on the bare TLD?
>
> Yes. If you'd read RFC 7085, you'd already know which ones do.
>
> There have been A and MX records at TLDs nearly as long as there have
> been TLDs.
And this is *why* I assumed you knew that, since the RFC is yours, and
makes precisely that distinction.
Cheers,
-- jra
--
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
