RE: [sitefinder-tech-discuss] followup from 15oct secsac

["Christopher X. Candreva" <chris@westnet.com>]

On Thu, 16 Oct 2003, Foster, Mark wrote:

> 1. Using the local "hosts" file to assign a different ip address for
> sitefinder.verisign.com (eg. 127.0.0.x)
> 2. Over-riding the sitefinder.verisign.com zone on the DNS servers you (or
> your ISP) control, in the same manner.
>
> Either method would either disable sitefinder (in a sense) or give you more
> control over where that traffic is directed.

Great. I'll be sure to send Verisign the bill for my time haveing to
implement this.

Alternatively, Verisign could
1) Not implement wildcards

2) Submit their search engine to the browsers for inclusion as a search
engine.

However, this does mark the first time I've seen Verisign admit in public
that the wildcard breaks something to the point that the user will have to
work around it. Thanks guys !


==========================================================
Chris Candreva  -- chris@westnet.com -- (914) 967-7816
WestNet Internet Services of Westchester
http://www.westnet.com/

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.elistx.com/unsubscribe>