Technical Contact and Network Solutions (now Verisign)
Good Morning: I was wondering, does anyone have a technical contact over at Verisign? We have a couple of domain names that we are trying to change the information on, and we are having technical problems changing the information (ie: which domain servers it should point to). I've called it into Verisign technical support earlier in the week, and they said "We have to send this over to engineering", and well, that's the last I've heard of it......everytime I call Verisign customer support, I get the same line "It's been sent over to engineering, and we can't find the status". I was hoping that someone might have a contact over a Verisign Engineering that could help us out... Thanks Spencer ************************************************************ Spencer Wood, Network Manager Ohio Department Of Transportation 1320 Arthur E. Adams Drive Columbus, Ohio 43221 E-Mail: Spencer.Wood@dot.state.oh.us Phone: 614.644.5422/Fax: 614.887.4021/Pager: 866.591.9954 *************************************************************
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. -- W . | ,. w , "Some people are alive only because \|/ \|/ it is illegal to kill them." Perna condita delenda est ---^----^---------------------------------------------------------------
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
participants (3)
-
David Lesher -
Lionel -
Spencer.Wood＠dot.state.oh.us