We have been given a report that Verisign's root whois server is being
(literally) hammered which is affecting their service. We're working on
minimizing the impact for this by performing only local lookups, but this
change may take a day or so. In the interim, Verisign is working on beefing
up their rate-limiting (except for "trusted" IPs).
These should help us minimize the impact.
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - chuck@tucows.com
> -----Original Message-----
> From: owner-discuss-list@opensrs.org
> [mailto:owner-discuss-list@opensrs.org]On Behalf Of Chris Scott
> Sent: June 25, 2002 11:53 AM
> To: discuss-list@opensrs.org
> Subject: WHOIS Problems
>
>
> Is anyone else seeing queries for OpenSRS domains against
> whois.opensrs.net
> returning:
>
> Unable to connect to whois.crsnic.net
>
> I'm getting this from command line and the OpenSRS Web site WHOIS. On a
> related issue, wouldn't the logic for a query search OpenSRS'
> database first
> and not need to go to crsnic.net to find the authoritative WHOIS
> if it finds
> a match--assuming that is what it is doing?
>
>
> --
> Chris Scott
> Host Orlando, Inc.
> http://www.hostorlando.com/
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:18 EDT