Looking for clue at NetSOL/Verisign
Is there anyone with a clue at verisign who's able to actually repair a broken entry in their database? I've got a companies domain name that seems to be stuck with nameservers listed in whois, but none in the .com zone. This means that everything for this companies domain is hitting the sitefinder crap, mail is being rejected, etc. A call to netsol got me a rather clueless person who claimed that sitefinder was created by ICANN, and that it's normal for a domain to have no nameservers for up to 3 days when changing name server entries. (instead of an immediate transition) I had this problem before with the exact same set of nameservers, it required a week worth of calls to verisign and a threat of legal action before someone manually touched something in their database to fix it. Unfortunately they claimed at the time that it was normal, and the changes had been processed normally (after a week!), so I have no contact information for the clued person who fixed it. -- Matthew S. Hallacy FUBAR, LART, BOFH Certified http://www.poptix.net GPG public key 0x01938203
On 9/20/03 6:33 AM, "Matthew S. Hallacy" <poptix@techmonkeys.org> wrote:
Is there anyone with a clue at verisign who's able to actually repair a broken entry in their database? I've got a companies domain name that seems to be stuck with nameservers listed in whois, but none in the .com zone.
LOL! I think we'll all see the next asteroid smack into the earth before you find anyone at Verisign who will respond to this! (on or off list) :-) -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net PGP: http://www.inoc.net/~dev/ Key fingerprint = A445 7D1E 3D4F A4EF 6875 21BB 1BAA 10FE 5748 CFE9 "I don't need parents. All I need is a recording that says, 'Go play outside!" - Calvin and Hobbes
On Sat, 2003-09-20 at 06:29, Robert Blayzor wrote:
On 9/20/03 6:33 AM, "Matthew S. Hallacy" <poptix@techmonkeys.org> wrote:
Is there anyone with a clue at verisign who's able to actually repair a broken entry in their database? I've got a companies domain name that seems to be stuck with nameservers listed in whois, but none in the .com zone.
LOL! I think we'll all see the next asteroid smack into the earth before you find anyone at Verisign who will respond to this! (on or off list) :-)
I suggest (Matthew) call network solutions back and tell them to call verisign NDS customer service. They are wrong about ICANN. -- Mark Foster <mark@foster.cc>
participants (3)
-
Mark Foster
-
Matthew S. Hallacy
-
Robert Blayzor