Re: Change to .com/.net behavior

[Vadim Antonov <avg () kotovnik com>]

I'm going to hack my BIND so it'll discard wildcard RRs in TLDs, as a
matter of reducing the flood of advertising junk reaching my desktop.

I think BIND & resolver developers would do everyone a service by adding
an option having the same effect.

Thank you, VeriSign, I will never do business with you again. You are as
bad as any spammer lowlife simply because you leave everyone with no
choice to opt out of your advertising blitz.

--vadim

On Mon, 15 Sep 2003, 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 () verisign com>
> VeriSign Naming and Directory Services