|
Click the comments link on any story to see comments or add your own. Subscribe to this blog |
30 Apr 2017
Among the many issues affecting ICANN's thousand new TLDs is collisions, that is, the same name already used elsewhere. The other uses are non-standard and unofficial, but some names turn out to have been used a lot. One approach to see how bad the collisions are is controlled interruption, in which the TLD publishes wildcard records with obvious impossible values, in the hope that systems that use colliding names see them and do something about it. The process is pretty simple. For 90 days the domain publishes records like these currently in the new .hotels TLD: hotels. 3600 in a 127.0.53.53 hotels. 3600 in mx 10 your-dns-needs-immediate-attention.hotels. hotels. 3600 in txt "Your DNS configuration needs immediate attention see https://icann.org/namecollision" hotels. 3600 in srv 10 10 0 your-dns-needs-immediate-attention.hotels. *.hotels. 3600 in a 127.0.53.53 *.hotels. 3600 in mx 10 your-dns-needs-immediate-attention.hotels. *.hotels. 3600 in txt "Your DNS configuration needs immediate attention see https://icann.org/namecollision" *.hotels. 3600 in srv 10 10 0 your-dns-needs-immediate-attention.hotels.When the 90 days are up, the domain takes out the interruption records, and starts putting in real ones. That's the theory, and what the ICANN registry agreements require. The practice turns out to be different.
|
TopicsMy other sitesOther blogsCAUCE A keen grasp of the obvious Related sitesCoalition Against Unsolicited Commercial E-mail |
© 2005-2020 John R. Levine.
CAN SPAM address harvesting notice: the operator of this website will
not give, sell, or otherwise transfer addresses maintained by this
website to any other party for the purposes of initiating, or enabling
others to initiate, electronic mail messages.