4 ms·
I once heard the story of a man who helped Aruba set up their DNS (.aw) in the late 90's. In exchange, as part of his compensation, he asked for an email addres
by herge 11y ago
I once heard the story of a man who helped Aruba set up their DNS (.aw) in the late 90's. In exchange, as part of his compensation, he asked for an email address at the top-level domain, and received something like js@aw, which is a perfectly functional email address, but trips up a lot of validators.
- hugi 11y agoDick move, though.
- marcosdumay 11y agoIt isn't a valid address. TLDs must not resolve, so it should be impossible to make a server handle it (yet, it is mostly possible, because most DNS servers do not completely implement the RFCs - still, there's no guarantee it will work on every network).
- Symbiote 11y agoThe first one I found that does resolve: http://ai./ http://ai./ It has an MX record too. There is nothing wrong with this.
- noinsight 11y agoIndeed - http://dk./ http://dk./ works too.
- breakingcups 11y agoIt is most definitely wrong, if your definition of wrong includes disallowed / not recommended by ICANN and IAB. What is wrong with it is, amongst other things, the real-world possibility of colliding with internal hostnames.
- dylz 11y agotk has address 217.119.57.22 cf mail is handled by 0 mail.intnet.cf. to has address 216.74.32.107 io mail is handled by 10 mailer2.io. gg has address 87.117.196.80
- vostok 11y agoI heard this story about Ian Goldberg, Anguilla, and the obvious email address.
- herge 11y agoIt might have been Anguilla, the story was told to me a long time ago.