nslookup tm
Non-existent domain
Browsers are able to reach them by forwarding to ac.com, ai.com or tm.com % dig a tm
; <<>> DiG 9.7.3 <<>> a tm.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41011
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;tm. IN A
;; ANSWER SECTION:
tm. 86366 IN A 193.223.78.213
;; Query time: 1 msec
;; SERVER: 192.168.66.32#53(192.168.66.32)
;; WHEN: Thu Jan 12 10:20:15 2012
;; MSG SIZE rcvd: 36
And also an open http server: % nmap tm.
Starting Nmap 5.00 ( http://nmap.org ) at 2012-01-12 10:24 BRST
Interesting ports on serv213.icb.co.uk (193.223.78.213):
Not shown: 997 filtered ports
PORT STATE SERVICE
80/tcp open http
113/tcp closed auth
443/tcp open httpsAnd yes, browsers redirect to .com if you jut put "tm", but at least Firefox loads the correct website if you put the whole URL, with http://
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: tm
Address: 193.223.78.213
Seems to be working for me.You should also note that email addresses that doesn't have a '.' in the host part are technically invalid, i.e. me@mytld is not a valid fully qualified email address.
You should also note that email addresses that doesn't have a '.' in the host part are technically invalid, i.e. me@mytld is not a valid fully qualified email address.
Hmm, has RFC 2822 been superseded? Because it clearly says the domain part can be a dot-atom, which is defined in the same RFC in ABNF form as:
dot-atom = [CFWS] dot-atom-text [CFWS]
dot-atom-text = 1*atext *("." 1*atext)
As you can see, the dot (".") is enclosed in a section of variable repetition (*) with no minimum number of times, so it can not appear at all.RFC 2822 has been superceded by RFC 5322. The problem is not being allowed to put MX records in the zone for a TLD, and hence the mail is not routeable. Also remember that you would need to differentiate between "me@mytld<.localdomain>" and "me@mytld.", I'm not sure if all MTA software (let alone MUA) will do the right thing with differentiation. This is probably considered to impact stability and hence is discouraged.
Not true, and you can see it yourself:
http://ac/
http://ai/
http://tm/
Nothing technically prevents a TLD from having an A record, it's just uncommon. So there could very well be http://microsoft/ or http://apple/, which would appear as "microsoft" and "apple" in FF and Chrome, at least.