[vox] COMPLAIN Verisign resolves unregistered .COM, .NET domains

Rod Roark vox@lists.lugod.org
Wed, 17 Sep 2003 09:41:57 -0700


On Wednesday 17 September 2003 09:15 am, p@dirac.org wrote:
...
> yup, i already sent letters to the ICANN and my cable provider, comcast.
> i asked comcast to install the patch to fix the breakage.
> 
> wierd.  just checked from a comcast IP and i can no longer connect to
> verisign's advertising page.  comcast's nameservers still return the
> advertising host's IP, but nobody's home.

That may be Comcast's doing.  I complained to my ISPs also,
Sonic.net and DSLExtreme, suggesting they apply the relevant
BIND patch.

Looks like Sonic.net has already rerouted the IP to one of
their own servers.  It gives me the default Apache page for
a new server.

$ /usr/sbin/traceroute 64.94.110.11
traceroute to 64.94.110.11 (64.94.110.11), 30 hops max, 38 byte packets
 1  adsl-64-142-15-1.sonic.net (64.142.15.1)  14.774 ms  15.296 ms  14.709 ms
 2  fast1-0-0.border.sr.sonic.net (208.201.224.194)  14.937 ms  14.638 ms  14.216 ms
 3  fast1-0-0.border3.sr.sonic.net (208.201.224.138)  14.945 ms  16.160 ms  14.719 ms
 4  serial4-0-0.border.200p-sf.sonic.net (64.142.0.86)  17.942 ms  22.007 ms  19.153 ms
 5  SONICNET-demarc.unitedlayer.com (209.237.229.249)  194.081 ms  234.434 ms  221.495 ms
 6  sitefinder-idn.verisign.com (64.94.110.11)  18.670 ms  17.229 ms  20.129 ms

-- Rod