Some Whois Lookup Services Might be Broken

It's only fair to share...1600

There are thousands of sites and services on the ‘net that offer domain name whois lookup services. As of last night many of them may have stopped working.

Why?

Many of them rely on fairly rudimentary software that parses the whois from Verisign (for .com and .net) and then relays the query to the registrar whois. The site or service then displays the whois output from the registrar’s whois server to you.

For “thick” registries, like .biz or any new TLD, the whois is always served directly by the registry whois server, so there’s no “referral” or extra parsing. Additional fields in thick whois therefore shouldn’t have much impact on most 3rd party whois lookup services.

So what happened?

Verisign, along with most other gTLD registries, updated their whois output last night to include some new fields namely the registrar abuse contacts:

Registrar Abuse Contact Email: xxx@xxxx.xxx
Registrar Abuse Contact Phone: +xxx.xxxxx

As a result of the changes a lot of software is currently “broken” as it simply cannot cope with the new output.

Is whois broken?

No. It’s working fine. The issue is with the software clients and how they are written. A lot of them were written years ago and have hardcoded in certain settings.

From what I can see the changes in whois output only seem to be impacting .com and .net whois lookups and only with *some* software. Doing whois lookups from my Mac’s command line, for example, still works fine for “thick” registries, but is failing miserably for .com and .net.

Will this impact registrars?

That depends.

Registrars generally do NOT use whois to check if domain names are available. Registrars tend to use EPP checks, zone files or other tools to see if a domain is taken or not. (And no, using DNS checks would be a terrible idea!)

There is a possible impact on *some* registrars when it comes to domain name transfers of .com and .net domain names.

However any impact is going to be short lived, as registrars will be aware of the issues and will update their software to handle the changes.

UPDATE: Here’s a fix for jwhois and similar software from Chris Pelling

In /etc/jwhois.conf (the location might vary)

find the line referencing “verisign-grs”:


}

“.*.verisign-grs.com” {
whois-redirect = “.*Whois Server: (.*)”;
}

and replace it with:


}
".*.verisign-grs.com" {
whois-redirect = ".*Registrar WHOIS Server: (.*)";
}


The above changes *should* help, though it will depend on which software you are using.

Thanks to Paul Goldstone for mentioning the issue to me first 🙂

It's only fair to share...1600