Skip to content
Register

What do you use for SSL on wildcard subdomains with budget DNS?

Web Hosting by tomhider 3 replies 174 views
tomhider

Member OP

Manchester

11 #1

The problem is wildcard ssl with budget dns and no api acess I have like fifty sudbomains on RackNerd and they dont give api keys unless you pay for the enterpirse tier which is stupid money so I been doing manual txt records every sixty days for the acme challenge and I keep forgettign and the cert expires and my users get the scary red page you know the one its a pain I tried using the http challenge but wildcard doesnt support it I think maybe I misread but anyway its a mess I looked at selfhosting acme but you still need the dns update right so whta do you all do for this I cant be the only cheap person here my wallet says no to Vultr dns api fees

sofialund

Member

homelab heatstroke

#2

¡the solution classic it is! The script cron with the records TXT manual ¡but boring! The provider cheap always has the limitations. I use the server old for the challenges, the proxy reverse with the nginx. The containers docker with the certbot! The automation partial is better that the manual complete. ¡the time saved, mate! You figure it out he says? ¡no! The patience with the budget DNS, necessary it is. The API hidden, sometimes exists. The support ticket, escalate it!

hot air, steady hand, magic smoke
SamAlvi

Member

Self-Host Everything

#3

I run my own authoritative nameserver in Docker Compose, acme.sh talks to it via nsupdate. Two containers: bind9 and a small webhook receiver. Reverse proxy in front, obviously. No API limits. No enterprise tiers. Total control. I've helped three friends migrate off budget DNS this way. The compose file is fifteen lines. Happy to share.

my cloud. my rules. my 3AM alerts.
RE

Member

3 #4

Sam you got a compose file for that or what

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft