Not sure if I understand you correctly. If you create a wildcard *.xx.xx, why would you have to create any other DNS records manually? Or do you want your clients to also manage their DNS to point it

(Quote)

Wouldn’t it be a lot easier to create a wildcard dns record to a loadbalancer ip? Or even start with one server? I guess you can then use WordPress Multisite.

(Quote)

(Quote)

Try dedicated IP. It will work.

Thank you for your answer, I understand my post lacked some informations so i've added a technical part. I already use CloudFlare and use a wildcard but i'm moving from CPanel, where my usecase is wor

You can easily point your wildcard subdomains to a dedicated IP.

(i'm already set with CloudFlare and CPanel, wildcard works, but i'm moving my hosting to DA)

(Quote)

* i've already a wildcard subdomain in my DNS zone

I can add a wildcard at *.bl.mxrbl.com so it can replicate the intent of mxtoolbox.

Wildcard SSL

Sorry that I didn't mention it, but I prefer single certificates to wildcard.

dns TXT record verification get * wildcard (Image)

and configure DNSSEC and other aspects including wildcard separately.

Now every domain added provisions its DNS on CloudFlare. It'll communicate with CloudFlare to authorize wildcard SSL as well as update DNS during server migrations. Likewise if you run multiple server

You could have used Ionic's ISAPI Rewrite Filter, or a wildcard handler (Image)

(Quote)

@BunnySpeed Any plans on adding wildcard support for purging URL lists?