Pointing a new site’s domain at your server has always meant leaving SpinupWP to add DNS records yourself. Now you can connect your DNS provider, and SpinupWP will manage A records for you, from when the site is created to when it’s deleted. We’re starting with support for Cloudflare and Amazon Route 53.
When creating or cloning a site, check Create DNS Record and SpinupWP will create (or replace) the domain’s A record to point at your server and issue a wildcard Let’s Encrypt certificate using DNS validation. HTTPS is enabled during site creation, without waiting for the new A record to propagate or coming back later to enable it. From then on, SpinupWP keeps the site’s A records in sync as you add or remove domains or change the primary domain. When deleting the site, you can choose to remove its records too.
The HTTPS screen now offers DNS validation for existing sites as well, which is handy if your site is proxied through Cloudflare or you want a wildcard certificate. Sites using DNS validation can also have wildcard additional domains, like *.turnipjuice.media, which previously required a custom certificate.
If you don’t connect a DNS provider, there’s still a small improvement for you. When you add a site whose domain already points at the server, SpinupWP now enables HTTPS automatically, instead of setting the site up with a SpinupWP subdomain (you can still turn one on from the Domains tab).
DNS providers are also available in the REST API. Check out the DNS Providers doc for setup instructions and more details.