Forum

Hi,

Do you disable the command Search during .com & .net drop time?


Thanks!

We still haven't seen anything like what you've described but, we do use all of our available Registry connections during drop times.  If a connection drops and we try to reconnect, sometimes that can be problematic because the Registry will think we're still at our max number of connections and are trying to open another. I'm not sure if that's the case here, but the connection issue does probably happen more often during drop times.

Not yet.  We haven't been able to replicate the error.  I can say, that we have interest in blocking our search function during drop times.  It really would not benefit us.

Have any other Dynadot users experienced this error?

Hi,

Any update on this?


Thanks!

No, we certainly do not disable search during these times.  Sometimes, the Central Registry is busy and we are unable to connect.  This happens occasionally at even non-drop times.  I am surprised to hear the error has appeared so constantly though. I will definitely ask our engineers to investigate when they return to the office tomorrow.  We'll post a reply here once we have more information.

OK. why then for 5 days in a row when I try to use the Search command I get this error exactly starting at 6:00 PM GMT to 7:00 PM GMT?

error,unexpected registry error

Again, this is not for one day but five. I just need a confirmation from you that you actually block/disable the Search command during COM/NET drop time.


Thanks.


 [This post has been edited by s_a_mansoura_eg on Sep 23, 2012 1:13am.]

No, we do not.