Domain Registrars

DNN: Network Solutions Sued

0

According to today’s post on DomainNameNews, a class action lawsuit was filed against Network Solutions and ICANN by the law firm of Kabateck Brown Kellner. The firm issued a press release announcing the action earlier today.
This is the second article written by Frank and Adam today about Network Solutions, the first being an article about the company monetizing a racially sensitive domain name owned by the NAACP, presumably to prevent links like this from being displayed.

Hidden Issue of "Ghost Records" at Domain Registrars

0

A few months ago, I encountered a problem at one of my registrars where domain names were still listed in my account even though I transferred these names out to buyers who used other registrars. While the Whois records displayed the correct ownership, these names were still showing up in my account. This was confusing as the names still looked like they were under my control, but I didn’t have any control over them and they weren’t really in my account.
I contacted my account manager who asked me to list all of the names that shouldn’t be listed in my account, so the issue could be resolved by technical support. I was afraid to do that, as I feared a mistake would lead to the cancellation of a domain name I owned. Since there were at least a few dozen of these names, and I have a significant number of domain names in this account, the process of going through my records would have been tedious. Also, since many of the names involved were average names that I had sold, it wouldn’t have been as obvious as some premium generics I sold, and I was afraid that I would accidentally list a name I still owned.
I had never experienced this “ghost record” issue at other registrars, so I put the question out there on a domain forum, and a number of people emailed me telling me that they had gone through the same problem with various registrars at some point. Fortunately, as luck would have it, I was contacted by Jason Lavigne, Business Development manager at Rebel.com & Pool.com, who gave me a suggestion to pass along to my registrar. With Jason’s permission to post, this is what he advised me to do:

“The problem can be greatly reduced by regularly running a script to check against the whois or by using the registry message queue. The registry message queue advises registrars every time a domain is added or removed from a registrar and is more reliable than using the whois. If a registrar checks their message queue daily for transfer away notices and then adjusts their database they should be able to minimize ghost records as we’ve done at Rebel.com.”

With this information, I emailed my account representative and asked to have the customer support group run the transfer away script against the Whois records. A couple of days later, these ghost records were all removed from my account, and the problem disappeared.
Thanks a bunch to Jason for that great advice!

Recent Posts

Snapnames to Run .UK Domain Name Auctions

I received emails from NameJet and SnapNames informing me about upcoming .UK domain name auctions that will be held via SnapNames. In case you...

Chief Acquires Brand Match Chief.com

Yesterday afternoon, I saw the tweet below from Lindsay Kaplan, Co-Founder of Chief, a private network and club for women executives. She was announcing...

Poll: Expiry vs. Private Auctions Bidding

I've been involved in a Twitter discussion with several people regarding the bidding on expiry domain name auctions and private domain name auctions. The...

IMI.com Registrant Prevails in Jury Trial

At the end of 2017, I wrote about the IMI.com UDRP decision. Shortly after the decision in favor of the complainant was published, I...

Links.com Sold for €700,000 via Sedo

Yesterday afternoon, Sedo reported the €700,000 sale of Links.com. At today's exchange rate, the sale is just shy of $800,000 USD (approximately $796,610), making...