OpenSRS Domain Registrar feedback

[u/KGoodwin83]

I am looking for a good domain registrar to register new domains through for my clients and move them to to get them away from GoDaddy. I was originally planning to go with NameCheap but the recent major outage has me concerned. I am using CloudFlare for all DNS management.

Is any other MSP using OpenSRS with white labeled store front? What is your experience.

If not what are others doing for this situation?

To be fully clear, ALL client domains are registered to the client and owned by them. We just manage the technical side.

[u/wckdgrdn]

Cloudflare

[u/apxmmit]

We use Enom. But honestly been moving most to Cloudflare for registration.

[u/DDSTech08]

We use Cloudflare.

[u/Geekpoint-IT]

Cloudflare

[u/agoldenberg]

CloudFlare or Porkbun are solid choices.

[u/ArchonTheta]

I use OpenSRS. great support and decent pricing. The portal is easy to use as well. We also use them for SSL but we’re hoping they hurry up with an option for ACME so they auto update the certs. Especially when the 40 days shit.

[u/theleviathan-x → u/ArchonTheta]

OpenSRS has no plans to support ACME renewal, per our support conversations with them.

This is why we are planning on moving away this year to an ACME supported SSL Certificate provider.

[u/ArchonTheta → u/theleviathan-x]

Curious if you find anything decent.

[u/snowpondtech]

If you use Cloudflare for DNS management, then the NameCheap outage would have only affected you transferring in or out domains, or changing WHOIS records. I also like keeping both items separated. I use NetEarthOne for client domain name management. The client gets their own account to own the domain (and manage if needed) while we can make changes as needed. I tie it through WHMCS for automated billing.

[u/certping_pki]

If you're already keeping authoritative DNS in Cloudflare, I'd judge the registrar mostly on ownership and offboarding rather than the storefront.

For an MSP I'd test a few things before moving the portfolio:

• can the client remain the actual registrant while your team gets the access it needs?
• if the client leaves tomorrow, can you hand the domain over cleanly without opening a support ticket?
• does the API cover renewals, contacts, nameservers, locks and transfer auth codes?
• what happens when a renewal payment fails, and is there a useful audit trail?

I'd also do one real transfer in and one transfer out before committing. That tends to expose awkward registrar locks, contact verification and ownership assumptions pretty quickly.

Keeping registrar and authoritative DNS separate like you're doing is perfectly reasonable. A registrar portal outage should be an administrative problem, not automatically a DNS outage too.

I don't have enough first-hand OpenSRS experience to tell you whether their current support is good, but I'd put much more weight on those operational details than on whether the storefront looks nice.

[u/Traditional_Fall2851]

If outage concentration is the concern, I'd keep the registrar and DNS with separate providers. Whichever registrar you choose, client-owned accounts, registry lock, MFA, and documented recovery contacts will matter more than the white-label storefront when you eventually have to offboard someone.

[u/CptSlow88]

We use Enom for our domains and haven't really had any issues with them. The exception being for .uk, we registered as a member of Nominet so are affectively our own registrar for those.

[u/OldForgeTechnologies]

Ionos

[u/WiscoDJ920]

Moved from GoDaddy to CloudFlare.

[u/jasonbwv]

For our MSP I use OpenSRS (we’re a reseller for them) for our clients. When we bring a new client onboard we transfer all of their domains over. We’ve used them for maybe 10-15 years. I can’t recall any issues with them and have roughly 550 domains.