> WHY we do it > Because a numeric TLD is something new. As far as we know, it has never been tested out in the open. > Because it means being independent from ICANN, and we believe this to be an important aspect of the experiment. > Because we CAN. And "we" also means YOU. Technically, the experiment works. It is not officially endorsed by the powers that be, but it Point 1 is pretty equivalent to #3 "because we can…
.42: new experimental, all numeric top-level domain
41–46 of 46 posts
Re: .42: new experimental, all numeric top-level domain
#42Earlier quoted context omitted.
reading the rules from an rfc mentioned on the wiki, if XXX.XXX.XXX.42 is a valid IP address, the client should try to use that first, if not it should only then try to use DNS to resolve.
Reference: http://tools.ietf.org/html/rfc1123#page-13 But note that the RFC assumes there will never be a numeric TLD. Furthermore, it suggests checking the string syntactically to determine if it's in dotted decimal form, remaining somewhat ambiguous about what to do if the hostname looks like IPv4, but the connection fails (it seems unwise to do a DNS lookup for every IPv4 address that's offline). Since IPv4 is rel…
host
The fully qualified domain name of a network host, or its IP
address as a set of four decimal digit groups separated by
".". Fully qualified domain names take the form as described
in Section 3.5 of RFC 1034 [13] and Section 2.1 of RFC 1123
[5]: a sequence of domain labels separated by ".", each domain
label starting and ending with an alphanumerical character and
possibly also containing "-" characters. The rightmost domain
label will never start with a digit, though, which
syntactically distinguishes all domain names from the IP
addresses.
http://www.ietf.org/rfc/rfc1738.txtRe: .42: new experimental, all numeric top-level domain
#43Before anyone wonders: No, this isn't an official TLD. The domains you register there won't resolve for anyone unless they futz with their nameserver settings. I'm not sure what to make of this. Looks like a bunch of hackers got really bored and perhaps had a beer too many...
Why can't we have our own TLDs - just like we have our own browsers and servers.
Re: .42: new experimental, all numeric top-level domain
#44Before anyone wonders: No, this isn't an official TLD. The domains you register there won't resolve for anyone unless they futz with their nameserver settings. I'm not sure what to make of this. Looks like a bunch of hackers got really bored and perhaps had a beer too many...
So what is an 'official' TLD? One that is controlled by an American government agency? Why can't we have our own TLDs - just like we have our own browsers and servers.
Re: .42: new experimental, all numeric top-level domain
#45Perhaps the 42registry should try to get openDNS to support .42, that would certainly open up a MUCH larger amount of people that its available to, its also reasonably easy to change to using openDNS servers.
Re: .42: new experimental, all numeric top-level domain
#46Before anyone wonders: No, this isn't an official TLD. The domains you register there won't resolve for anyone unless they futz with their nameserver settings. I'm not sure what to make of this. Looks like a bunch of hackers got really bored and perhaps had a beer too many...