I have to agree with William -- anybody who visits the OpenSRS site (or who
links to it under the covers) is doing so because it is MOST likely to have
updated information about the domain. It should first attempt to query its
own internal database and THEN look to CRSNIC if no information is found.
Perhaps switching the order and adding a small disclaimer is the best
solution? Something like "This information is correct to the best of our
knowledge, but due to the process used to update domain names may not be
completely accurate."
Regards,
Eric Longman
Atl-Connect Internet Services
+-------------------------------------------------------+
| Atl-Connect Internet Services http://www.atlcon.net |
| 3600 Dallas Hwy Ste 230-288 770 590-0888 |
| Marietta, GA 30064-1685 [EMAIL PROTECTED] |
+-------------------------------------------------------+
----- Original Message -----
From: "William X. Walsh" <[EMAIL PROTECTED]>
To: "Charles Daminato" <[EMAIL PROTECTED]>
Cc: "Ross Wm. Rader" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, November 28, 2000 1:52 PM
Subject: Re[5]: PLEASE Fix the whois server once and for all
Tuesday, November 28, 2000, 9:49:42 AM, you wrote:
>> We must build our logic within the constructs of these assumptions - in
>> brief the whois will likely remain in its current functionality which has
>> worked for 99% of you for almost a year.
I just wanted to sum this up. The bottom line is that the current
method of doing things is causing no results at all to come up many
times for users who query whois.opensrs.net to get the whois
information for their own domain names.
This is how it came back into the forefront of my own list of things
that need to get resolved. Customers complaining about getting only
"Unable to contact crsnic" when trying to see the whois on their own
data. And I tested it myself last evening and got this result many
many times.
No other prominent registrar is running their whois this way, so I
don't buy the "we have to do it this way" argument. All other
registrars who do recursive lookups do it only if they get no local
matches.
--
Best regards,
William mailto:[EMAIL PROTECTED]
