My team and I are creating a service that when user request, it creates a new server instance on the fly, with a different IP for each new instance. The issue is that I’m connecting from a client via WebSockets to that newly created server. But I need it to be SSL certificated. So I can’t use just the IP.
So, what I’m thinking is to create a subdomain for each one of this server instances. The only issue here is that I need the subdomain to be available super quick, and I don’t know if I can trust the DNS propagation times for this.
Is there any solution to this? Like having my own routing server that have a Wildcard Subdomain and then route the traffic based on that? I think I can’t use Apache or those kind of solutions because it’s not only HTTP/S traffic that I’m handling.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I’ve built a system like this for a side project using the DO API to create and update A records when new droplets are created. Personally I’ve never run into propagation issues using this method and subdomains are available pretty much instantly.
If you do have concerns about this option your best bet may be to self-host your DNS so you would have full control over your TTL settings.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.