Hello,
After some more testing, I've confirmed that .biz is causing some
serious delay's. On our site, we run lookups for all 5 extensions (.com,
.net, .org, .biz. and .info) when someone searches for a name. However, over
the past few weeks, we have been noticing the overall response time taking
much longer (in the upwards of 30+ seconds every 1 out of 4 lookups or so).
However, after doing some testing today, and removing .biz from our default
lookup array, our overall response times are back to around 4 seconds. Can
anyone else confirm or provide some feedback?
Thanks,
Nitin
----- Original Message -----
From: "Charles Daminato" <[EMAIL PROTECTED]>
To: "Nitin Agarwal" <[EMAIL PROTECTED]>
Sent: Monday, January 07, 2002 9:26 AM
Subject: Re: .biz caught null error taking long time
That typically happens when the registry doesn't send us a response to a
command. If you can send me the dates and times of these errors, I can
pass it on to our dev and ops teams so they can do further looks to notify
the registry.
Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]
On Mon, 7 Jan 2002, Nitin Agarwal wrote:
> Hello Charles,
>
> Just wanted to make you aware of an issue (if you already aren't).
I've
> noticed over the past few weeks (since 12/11/01 according to my logs) that
a
> new occasional error has been happing when searching for .biz domain
names.
> I get the response "Unexpected response received from the Registry: [433]
> [Caught: null]". This is not traceable. However it does happen. Could you
> shed some light on the meaning and reason of this error or how it can be
> fixed? One thing I have noticed is that the lookup takes a very long time
> before this error comes.
>
> Thanks,
> Nitin Agarwal
>
>
