[48259] in North American Network Operators' Group
Re: Technical Contact and Network Solutions (now Verisign)
daemon@ATHENA.MIT.EDU (David Lesher)
Sat May 25 03:04:20 2002
From: David Lesher <wb8foz@nrk.com>
To: nanog@merit.edu (nanog list)
Date: Fri, 24 May 2002 06:04:08 -0400 (EDT)
In-Reply-To: <jvgseu0o3s3u4he56u8vi3k54sffu43m1d@4ax.com> from "Lionel" at May 24, 2002 11:49:13 PM
Reply-To: wb8foz@nrk.com
Errors-To: owner-nanog-outgoing@merit.edu
Unnamed Administration sources reported that Lionel said:
>
>
> On Fri, 24 May 2002 09:23:15 -0400, Spencer.Wood@dot.state.oh.us wrote:
>
> [standard Netsol/Verisign incomptetance snipped]
>
> >I was hoping that someone might have a contact over a Verisign Engineering
> >that could help us out...
>
> Phoning them has been known to work, but the probability is on a par
> with that of having a rain of live frogs. The industry-standard solution
> to this problem is to yank your domains out from under them & put them
> somewhere else, then to ignore all the fake 'invoices' they send you
> afterwards.
The proven alternative contact approach is just sue them.
This seems to penetrate to a level where you can get a
response. It's a pity it's needed but....
--
A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433
