[dns-operations] Hearing first complains about failing internal resolving due to .prod TLD

Rubens Kuhl rubensk at nic.br
Sat Sep 13 16:10:09 UTC 2014

> I’m not sure why the dot prod was not first set up to return NXDOMAIN, queries logged, and then source IP contacted to warn them of such upcoming change.
> May be this is an insight now, may be this is something to do for ALL newly introduced TLDs, set up the resolution for a month with NXDOMAIN and then analyze the logs and see if it could be an issue.

Such query logging could be seen as front-running, which is forbidden by ICANN contracts. An idea similar to what you mentioned has been floated in the new gTLD program, but has been withdrawn due to large criticism from the community, including RIRs. 

What we tried was to contact the users that were likely to be more affected by collisions when the queried name allowed us to infer who would be affected, following information from this report:

We had 0% of responses of such contacts, indicating that was likely that a massive mailing of IP space contacts wouldn't have much of a effect anyways. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20140913/6b294d9d/attachment.html>

More information about the dns-operations mailing list