Change to .com/.net behavior

Tue Sep 16 00:16:28 UTC 2003

You mean you have been studying a way for more people to buy domain through you.

I also am modifying BIND to convert your wildcard #$%^^% to NXDOMAIN.

Between the domains that I have with you and all the problems we've had with it
each time you 'change' your web interface, I've already made my decision to
avoid VeriSign/NetworkSolutions for rest of my life.

Before I figure out this BIND thing, for now..

box02jp5-cr01.twdx.net# set routing-options static route 64.94.110.11/32 discard;

-hc

-- 
Sincerely,
  Haesu C.
  TowardEX Technologies, Inc.
  WWW: http://www.towardex.com
  E-mail: haesu at towardex.com
  Cell: (978) 394-2867

On Mon, Sep 15, 2003 at 07:24:29PM -0400, Matt Larson wrote:
> 
> 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 at verisign.com>
> VeriSign Naming and Directory Services