So the wildcard DNS is indeed gone now

Customer has ava.hosting in resolv.conf, ava.hosting has wildcard dns for this domain.

If the customer installed from template and the template contains a resolvconf like this, it's entirely the provider's fault, for having such a template along with the wildcard DNS.

doing host www.msftconnecttest.com would resolve www.msftconnecttest.com.ava.hosting and could get 176.123.0.130 because wildcard A record.

Wildcard DNS records rocks! (Image)

I've dabbled with using DNS for wildcard domains (because you can't use HTTP authentication for wildcards). The basic certbot install on debian 11 (1.12.0) and 12 (2.1.0) don't have support for this o

(Quote)

In short, I just have to add domain to NameCrane (with all the MX and TXT records and a wildcard subdomain TXT for SPF) so that I can forward all the emails a.k.a catch-all to any of my subdomains* (n

(Quote)

(Quote)

You can set a custom SSL hostname inside of cranemail. By default this will normally be mail.domain.tld. Not aware of any way to have both mail.* and cloud.* pointing to it short of... a wildcard I gu

(Quote)

Does CraneMail have a wildcard alias function?

almost a decade ago i paid @xoxo around 2 bitcoins for few wildcard ssl certificates that he was reselling. From the lil info I had, he appeared to be a chinese national.

Free Wildcard SSL Certificate

(Quote)

(Quote)

(Quote)

Yes, a wildcard 'catch-all' is available if that's your thing.

Are you wanting to us a wildcard catch all or would you add specific aliases?