Yeah, it does work! Nice.
If you want to continue to use the wildcard cert, setup your DNS approp:
For ex:
# does not work because no such dns entry
curl https://random-63-chars.json.media -v
# works because the query is resolved ahead-of-time with the right ipv4
curl https://random-63-chars.json.media --resolve 'random-63-chars.json.media:443:37.16.14.11' -v
Create a wildcard DNS entry through Fly dashboard, or if you’re ambitious, then via flyctl
or Fly’s graphql endpoint.
Basically, dig random.json.media +short
should return the same IPv4 as dig www.json.media +short
(likewise for IPv6: dig AAAA random.json.media +short
).
Or, you could delete the wildcard cert and generate just the one for www.json.media
, if that makes sense?