As an OpenSRS reseller I can do nothing when another registrar has a problem,
But I can have a tool that monitors the OpenSRS whois for OpenSRS domains.
That tool can notify the domain name holder when the Whois information on his/her
domain is altered.
In addition the tool can be built to check the registry whois whenever a change is noted
in the OpenSRS whois to report the two whois results to the domain holder.
these issues are more important for contact information. as far as nameserver issues, I already
download the zone files for biz info com net and org daily and log all changes so info on those changes
can be parsed directly from the daily zone files.because if a nameserver gets messed up in the zone files it might
not reflect in a whois.
I already can tell you if your nameserver changes or if your domain is deleted from the zone files (those tools are already built)
and any tool on the internet needs to come with it's own set of disclaimers...
But this is a tool to be built for our customers hopefully with the co-operation of Tucows so assist us in servicing our customers - and indirectly theirs.
Michael
At 08:46 PM 2/5/2005, Chuck Hatcher wrote:
> George, > > That is an excellent idea, but I would limit the tool to domains > registered through OpenSRS.. Make the service free but you the domain > must be registered through us for the service to work. We can not be > responsible for the (in)accuracy of whois data with domains registered > through other registrars.
Can you even be responsible for the accuracy of whois data for domains registered through OpenSRS? I mean, if the purpose of the tool is to let the registrant know when something bad happens, and something bad does happen, and the tool fails to tell the registrant, what will OpenSRS do? Nothing? Refund the registration fee?
I bring this up not because OpenSRS has a history of bad whois information, although I have encountered cases where bulk name server updates at OpenSRS correctly updated the registry and the zone, but did not update the OpenSRS whois data. But I have experienced many cases at other registrars where registrar data was out-of-synch with the registry. This is why I use third party tools to monitor my domain names. It's an independent check that quickly brings attention to cases where things are not as they seem. I have had dozens of domain names at a large four-letter registrar that were shown as locked in their system, but unlocked according to the registry whois. Guess who I believe? I have had dozens of .info domain names at a famous "high-security" registrar that had completely different contact information in the control panel and registrar whois, compared to Afilias' whois. I have had several domain names at a well-known German registrar whose whois consistently showed an extra year remaining compared to the registry, and the registry is correct according to the amount of money I paid. What will they do when the name expires (and is auto-renewed) at the registry? Who knows? But I am aware of the problem. And think of how common the problem is of registrars continuing to show (and send renewal notices for) domain names that have been transferred to other registrars. This is the information we need to know, even when the registrar doesn't.
I don't mean to sound skeptical, but as long as registrars disclaim all responsibility for errors in their registration agreements, I'm going to do my own monitoring!
