Regular people (non technical) don’t want to mess around with DNS records and I was wondering if there was a way to have a single validation for the root and www using Fly’s network.
Yep! It’s actually just the AAAA record that’s required, but there’s almost no reason people just want IPv6. This is required for apex domains, since you can’t have CNAME records for the example.com.
The CNAME for www also issues the certificate automatically. CNAMEs work great for www.example.com.
All they need for the www. subdomain is a CNAME. We’d just tell people to use CNAMEs for everything if they worked for the “apex” domain. They will (unfortunately) need to add A/AAAA records for apex domains.
I created a cert for domain.com. I then added the A and AAAA records and now the cert is shown as ready.
So then I created the cert for www.domain.com. Then added a CNAME record www.domain.com -> domain.com. And now the cert shows as ready.
Is this even legal?
Edit:
Obviously it’s “legal” from a DNS standpoint. @kurt I was wondering if I’m shooting myself in the foot as far as cert creation with Fly is concerned by doing that?