North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: ICANN opens up Pandora's Box of new TLDs

  • From: David Conrad
  • Date: Mon Jun 30 08:42:07 2008

On Jun 30, 2008, at 1:53 AM, Phil Regnauld wrote:
	But considering the amount of flag waving and "Caution: Wet
	Floor" signs ICANN placed when it rolled out something has
	harmless as the IDN tests in the root, I'm surprised that they
	haven't thought about all the non-FQDNs that will suddenly
	resolve, including all the private TLDs that people use
	internally.

1) The new gTLD stuff hasn't gotten as far as the point where the testing of IDN stuff started.
2) ICANN (or rather, the technical side of ICANN staff) has thought about this and there is a 'technical evaluation' phase of the application evaluation
3) We've already run into the 'private TLD' thing: lots of global companies (apparently) have internal domains organized on regional/ continental boundaries. When '.asia' was put into the root, the Internet did not break.


	The other way around.  And if I ping 'dk', my resolver
	stops after "catpipe.net" and my other private domain.
	It doesn't try "dk.", even though dk. has an A record
	associated with it.  I get NXDOMAIN.

Your resolver appears to be broken. Works for me:


% dig +short dk
193.163.102.23
% traceroute dk.
traceroute to dk (193.163.102.23), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 4.484 ms 3.933 ms 1.163 ms
2 * * *
3 * ge-2-14-ur01.santaclara.ca.sfba.comcast.net (68.86.248.65) 13.600 ms 10.250 ms
...
20 netgroup.r2.dk-hostmaster.dk (217.116.254.58) 204.900 ms 200.835 ms 199.208 ms
^C


(doesn't appear to answer to pings)

Regards,
-drc