unqualified domains, was ICANN to allow commercial gTLDs
rps at maine.edu
Mon Jun 20 17:28:46 UTC 2011
Now that the cat is out of the bag, maybe we should look at trying to
get people to make use of FQDN's more.
I just added a rewrite to my person site to give it a try, and threw a
quick note up about it:
So far, it looks like every browser correctly respects the use of a
FQDN; though it looks like SSL is completely broken by it. The
solution there is either to generate certificates with the correct
FQDN CN, or to make browsers assume that every CN is a FQDN (better
To be honest, I think we've all been a little lazy leaving off the
last dot and are just annoyed now that it's going to cause a potential
On Fri, Jun 17, 2011 at 9:33 PM, John Levine <johnl at iecc.com> wrote:
>>The notion of a single-component FQDN would be quite a breakage for
>>the basic concept of using both FQDNs and Unqualified names.
> Well, you know, there's a guy whose email address has been n at ai for
> many years. People have varying amounts of success sending him mail.
Epic Communications Specialist
Phone: +1 (207) 561-3526
Networkmaine, a Unit of the University of Maine System
More information about the NANOG