Top-level domain registries process registration and management requests in one of two ways: synchronously or asynchronously. The type of registry behind a TLD determines how quickly a change takes effect and what you should tell customers when they place an order.
How synchronous registries work
A synchronous registry processes requests in real time. When you submit a registration or update, the server responds immediately with either confirmation of the change or an error explaining why it could not be completed.
Because there is no waiting period, customers see the result of their request right away.
How asynchronous registries work
An asynchronous registry accepts a request, then reviews it before applying any change. This creates a "wait state" where you and your customer have submitted the request but the registry has not yet acted on it.
Once the registry processes the request, the system updates and OpenSRS sends a notification to confirm the change.
Expected processing times
Processing time on asynchronous registries varies. Registrations are typically completed in under five minutes, but they can take longer for reasons outside our control.
Note: Set realistic expectations with customers when they place an order on an asynchronous TLD. Let them know the registration may take a few minutes to confirm, and that they will receive a notification once the registry completes the request.
Next steps
- Identify which TLDs you sell are asynchronous. Build a quick reference so your support team knows when to expect a wait state.
- Update your order confirmation messaging. Tell customers ordering asynchronous TLDs that the registration completes after the registry processes the request.
- Train your support team on wait states. Make sure agents know how to explain pending registrations and what notifications customers should expect.
Questions? Contact OpenSRS Support.
How helpful was this article?
Thanks for your feedback!
Do you still need help? If so please submit a request here.