Hi,
since I haven't received an answer from [EMAIL PROTECTED] in almost a
week, I'll post my question here.
I'm not using reg_system.cgi, so I see (and log) domain registration
errors. We very rarely get a legitimate "Domain Taken" error, because we
check if the domain is available before validating the registration request.
Last week my backend attempted the registration for the domain
"creaptiva.com", and received a "Authentication Error: Unrecognized Peer."
This was at 13.15 CET, or in the middle of the night in Canada. About four
hours later I manually rescheduled the registration, and got a "Domain
Taken." error.
I had this problem a lot in the past, and as an additional hassle the
domain would get registered with the default nameservers provided in the
resellers.opensrs.org interface (which I hadn't updated) instead of the
ones sent through the API, and I had just thrown away the user password
thinking the domain registration failed.
Just minutes ago I got an "Unable to establish socket." error. Hopefully
this is a real error and the domain didn't get registered.
Let's just for a moment ignore the lack of any interface on registrar
transfers -- I'll just poll the pending order list from the reseller
interface for the time being.
Since I'm trying to get my side of the system in a stable state, it would
be at least reassuring to know that 0's are 0's and 1's are 1's: I want to
be sure that when I get an error it really is an error, and my domain is
not registered.
It would also be nice to know that the registration system is stable even
when it's not babysitted by opensrs staff in Canada, but if 0's are 0's
I'll just poll until the domain gets registered.
People using reg_system.cgi should also be concerned, as they might be
losing sales (or paying for domains that customers are unable to use)
because of the reliability problems.
Duncan
