sitefinder-tech-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [sitefinder-tech-discuss Home]


Subject: Re: [sitefinder-tech-discuss] Pseudo code please


As far as I'm concerned, WILDCARDS do not belong in any ZONE file which contains
NS records that refer to servers not controlled by the administrator of the ZONE
file.

However, if one were to make an exception to that, such exception should be very
carefully constrained.  I don't know what the best exact boundary is.  I can
tell you for certain that .com, .net, .org, .edu. .gov are outside of it.  I
can't tell you for sure that there is a TLD where it is a good idea.
And, just in case anyone is this insane, I assure you that "." is definitely
_NOT_ an acceptable candidate.

Owen


--On Thursday, October 23, 2003 08:11:39 PM -0400 Andrew Newton <anewton@verisignlabs.com> wrote:

Owen DeLong wrote:

       Hand count the number of NS records in .MUSEUM.
       Hand count the number of NS records in .US
       Hand count the number of NS records in .COM
       Hand count the number of NS records in .NET

The point is well understood:  size matters.  However, how do you quantify that.  More than 1,000 domains?  More than 10,000?  100,000? Where's the cut-off?  And how do you arrive at the number?

You'll get no argument here.  There do no appear to be guidelines for
this.  However, VeriSign would be willing to participate in their
creation.

Cool... I guess what is needed is a comment on the applicable RFC that
reads something like:

Actually, I was speaking of best practices for deploying a wildcard in a TLD.  The issue of the "right" to do it is not technical.

-andy




Attachment: pgp1bCwe2zp7E.pgp
Description: PGP signature



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [sitefinder-tech-discuss Home]


Powered by eList eXpress LLC