Re:It's Way Too Easy to Get a .gov Domain Name
by FDSGSG on Wednesday November 27, 2019 @07:11AM
(#21647204)
This prohibition only applies to gTLDs. It does not apply to ccTLDs.
Re:It's Way Too Easy to Get a .gov Domain Name
by lifthrasiir on Wednesday November 27, 2019 @08:27AM
(#21647612)
Aha, thank you for pointing it out---I actually overlooked a very informational RFC that says exactly this [1].
Re:It's Way Too Easy to Get a .gov Domain Name
by Symbiote on Wednesday November 27, 2019 @03:52AM
(#21646312)
http://ai./ is a better example.
Re:It's Way Too Easy to Get a .gov Domain Name
by notatoad on Wednesday November 27, 2019 @02:22PM
(#21651049)
both pn and ai are giving me DNS errors in chrome on ubuntu.
Re:It's Way Too Easy to Get a .gov Domain Name
by Symbiote on Thursday November 28, 2019 @12:20PM
(#21658858)
The DNS server at work (which I maintain... oops) doesn't work, but home and other servers do work:
host ai. 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
ai has address 209.59.119.34
ai mail is handled by 10 mail.offshore.ai.
Re:It's Way Too Easy to Get a .gov Domain Name
by eru on Wednesday November 27, 2019 @12:26AM
(#21645489)
HN doesn't like your link's formatting. Try: http://www.pn./ or http://www.pn/
Re:It's Way Too Easy to Get a .gov Domain Name
by CydeWeys on Wednesday November 27, 2019 @10:48AM
(#21648817)
This unintentionally makes a point about how hard these domains are to use; they're not supported very well.
Re:It's Way Too Easy to Get a .gov Domain Name
by LukeShu on Wednesday November 27, 2019 @12:44PM
(#21650080)
The problem is the closing ` is being treated as part of the URL.
Re:It's Way Too Easy to Get a .gov Domain Name
by distances on Wednesday November 27, 2019 @02:00AM
(#21645884)
Your .pn link doesn't work for me without www part.
At least for https://www.fi/ the case is that someone registered "www" as the domain name in the early days.
Re:It's Way Too Easy to Get a .gov Domain Name
by lifthrasiir on Wednesday November 27, 2019 @02:29AM
(#21645999)
Hmm, I guess the current browsers simply don't like such domain and automatically put www. At the very least, the Google DNS gives the following:
ai. 209.59.119.34
cm. 195.24.205.60
dk. 193.163.102.58
gg. 87.117.196.80
je. 87.117.196.80
pn. 80.68.93.100
tk. 217.119.57.22
uz. 91.212.89.8
ws. 64.70.19.33
But I agree that these domains are now out of luck, given that browsers no longer even remotely support them.
Re:It's Way Too Easy to Get a .gov Domain Name
by tropo on Wednesday November 27, 2019 @11:45PM
(#21654636)
I see that the Vatican has given up. Long ago, http://va/ was it. No other name under va existed. Netscape Navigator was able to navigate to that part of the net.
It really did make sense for such a tiny place.
While it is prohibited by the ICANN policy [1], it is not strictly enforced so that there are multiple TLDs with A/AAAA records. They traditionally could be resolved with a trailing dot (thus it is not a dotless host name, that would have no dot), but nowadays many browsers refuse to resolve them without an explicit scheme. But they do still exist: try `http://pn./` for example.
[1] https://serverfault.com/a/907228