Non consistent whois responses

[umpirsky]

I noticed that whois result varies for same domain from time to time, here is an example (umpirsky.com):

string(2426) "\nWhois Server Version 2.0\n\nDomain names can now be registered with many different competing registrars. \nGo to http://registrar.verisign-grs.com/whois/ for detailed information.\n\nNo match for "UMPIRSKY.COM".\n\n>>> Last update of whois database: 2013-06-02T09:51:14Z <<<\n\nNOTICE: The expiration date displayed in this record is the date the \nregistrar's sponsorship of the domain name registration in the registry is \ncurrently set to expire. This date does not necessarily reflect the \nexpiration dat"...

string(2733) "\nWhois Server Version 2.0\n\nDomain names in the .com and .net domains can now be registered\nwith many different competing registrars. Go to http://www.internic.net\nfor detailed information.\n\n Domain Name: UMPIRSKY.COM\n Registrar: ACTIVE 24 AS\n Whois Server: whois.active24.com\n Referral URL: http://www.active24.com\n Name Server: NS1.LOOPIA.SE\n Name Server: NS2.LOOPIA.SE\n Status: ok\n Updated Date: 01-apr-2013\n Creation Date: 02-apr-2008\n Expiration Date: 02-apr-2014\n\n>>> L"...

Related issue umpirsky/wisdom#16

It is easily reproducable for single or multiple domains with wisdom, as well as naked whois. I reproduced by runing https://github.com/umpirsky/wisdom/blob/master/examples/check.php several times in a row getting different results.

Note: wisdom is using "react/whois": "0.1.*".

[igorw]

It's actually a bug in react/dns. Currently it only checks for A records. It should be following the chain of CNAMEs as well.

[umpirsky]

@igorw Thanks. Should I open issue in react/dns repo?

[igorw]

I've submitted a patch, please test it.