Problems with NS*.worldnic.com

Tue Apr 26 02:37:21 UTC 2005

Well, the first thing any engineer worth their saly would
ask in a situatin such as this is "Were any changes implemented,
concurrent with the appearance of these problems, which would
have possibly account for this?"

This problem has fairly wide-spread implications, it would
appear, and the lack of technical information on it is
rather alarming...

- ferg

-- Matt Larson <mlarson at verisign.com> wrote:

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 at verisign.com>
VeriSign Naming and Directory Services

--
"Fergie", a.k.a. Paul Ferguson
 Engineering Architecture for the Internet
 fergdawg at netzero.net or fergdawg at sbcglobal.net
 ferg's tech blog: http://fergdawg.blogspot.com/