Discuss mailing list

[Jeff Taylor <shdwdrgn AT sourpuss.net>]

Just an update to this... I've been doing some digging in the root zone, and it appears that both the opennic and icann NS server entries are being added, overlapping.  This is probably why some servers are getting the wrong zone files.  I'll see what I can do over the weekend to resolve the conflict and make the script notify me when other conflicts come up in the future.

On 12/20/2014 11:51 AM, Jeff Taylor wrote:

ICANN appears to have activated their own .ing TLD this week.  I'm starting to see tier-2 servers failing due to receiving zone files from the ICANN side rather than the OpenNic copy, so we either need to take measures to disable the ICANN version from opennic servers, or we need to vote to shut down our own .ing TLD.

For those interested, please check the SOA for your .ing zone:
# dig +short SOA ing. @my_server

OpenNic reply: ns5.opennic.glue. hostmaster.dns.ing. 2014031302 3600 3600 604800 86400

ICANN reply: ns-tld1.charlestonroadregistry.com. dns-admin.google.com. 268435537 21600 3600 1209600 300

Since Tim has already said he is not interested in fighting to retain the .ing zone I would like to call for a vote to drop the zone.  We could certainly add another TLD later to replace it, but for now we need to resolve the conflict.

--------
You are a member of the OpenNIC Discuss list. 
You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org