[80113] in North American Network Operators' Group

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

Re: Problems with NS*.worldnic.com

daemon@ATHENA.MIT.EDU (Matt Larson)
Mon Apr 25 21:59:29 2005

Date: Mon, 25 Apr 2005 21:58:58 -0400
From: Matt Larson <mlarson@verisign.com>
To: Randy Bush <randy@psg.com>
Cc: Greg Schwimer <gschwimer@godaddy.com>, nanog@nanog.org
In-Reply-To: <17005.35372.730623.208318@roam.psg.com>
Errors-To: owner-nanog@merit.edu


On Mon, 25 Apr 2005, Randy Bush wrote:
> i don't think this
> 
>     roam.psg.com:/usr/home/randy> doc -p -w worldnic.net
>     Doc-2.1.4: doc -p -w worldnic.net
>     Doc-2.1.4: Starting test of worldnic.net.   parent is net.
>     Doc-2.1.4: Test date - Mon Apr 25 14:20:45 HST 2005
>     ;; res_nsend: Protocol not supported
>     DIGERR (UNKNOWN): dig @a.gtld-servers.net. for NS of worldnic.net. failed
>     ;; res_nsend: Protocol not supported
>     DIGERR (UNKNOWN): dig @b.gtld-servers.net. for NS of worldnic.net. failed
> 
> is the worldnic problem, but could be.  but it is a problem.

a.gtld-servers.net and b.gtld-servers.net have AAAA records.  Some
applications and stacks try the v6 address first if it's available and
will appear to hang if you don't have v6 connectivity.  That may very
well be what's happening here.

Matt
--
Matt Larson <mlarson@verisign.com>
VeriSign Naming and Directory Services

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