WATPA: Verisign breaks .com / .net

From: Christopher X. Candreva <chris@westnet.com>
Date: Mon Sep 15 2003 - 20:19:43 EDT

Verisign is returning an IP for all unregistered domains -- and all domains
without name servers -- directed it to their search web page. Of course,
this machine is now takeing traffic for any other service someone tried to
access by mistake.

This means no more 'host not found'. This means if you mistype an e-mail
address, you can't get an error immediately -- it's all going to Verisign's
mail server. If their server is down, you won't get an error for days
possibly. Thanks Verisign.

Never mind anyone trying to test any other service. Mistype the domain,
you don't get the error you expect. This breaks an incredible amount of

I realize we are only Westchester based, but anyone know anyone higher up
the Govt chain ? Norm ?

From: Matt Larson <mlarson@verisign.com>
Subject: Re: Change to .com/.net behavior

> Today VeriSign is adding a wildcard A record to the .com and .net
> zones. The wildcard record in the .net zone was activated from
> 10:45AM EDT to 13:30PM EDT. The wildcard record in the .com zone is
> being added now. We have prepared a white paper describing VeriSign's
> wildcard implementation, which is available here:
> http://www.verisign.com/resources/gd/sitefinder/implementation.pdf
> By way of background, over the course of last year, VeriSign has been
> engaged in various aspects of web navigation work and study. These
> activities were prompted by analysis of the IAB's recommendations
> regarding IDN navigation and discussions within the Council of
> European National Top-Level Domain Registries (CENTR) prompted by DNS
> wildcard testing in the .biz and .us top-level domains. Understanding
> that some registries have already implemented wildcards and that
> others may in the future, we believe that it would be helpful to have
> a set of guidelines for registries and would like to make them
> publicly available for that purpose. Accordingly, we drafted a white
> paper describing guidelines for the use of DNS wildcards in top-level
> domain zones. This document, which may be of interest to the NANOG
> community, is available here:
> http://www.verisign.com/resources/gd/sitefinder/bestpractices.pdf
> Matt
> --
> Matt Larson <mlarson@verisign.com>
> VeriSign Naming and Directory Services
Received on Mon Sep 15 20:19:44 2003

This archive was generated by hypermail 2.1.8 : Mon Sep 15 2003 - 21:55:01 EDT