[105731] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

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

daemon@ATHENA.MIT.EDU (Phil Regnauld)
Mon Jun 30 09:16:11 2008

Date: Mon, 30 Jun 2008 15:15:57 +0200
From: Phil Regnauld <regnauld@catpipe.net>
To: David Conrad <drc@virtualized.org>
In-Reply-To: <3BB28A67-1837-4374-A5F5-574EB05853E2@virtualized.org>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

David Conrad (drc) writes:
>
> 1) The new gTLD stuff hasn't gotten as far as the point where the testing 
> of IDN stuff started.

	Mhh, ok :)

> 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

	Fair enough.

> 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 doesn't use the resolver the same way other applications do.

	Try "ping dk" vs "ping dk.", or "telnet dk" vs. telnet "dk."

	Of course, depends on the OS -- but at least on a few BSDs (OS X, FreeBSD),
	Linuxes (Debian, Ubuntu), it behaves the same way.



home help back first fref pref prev next nref lref last post