• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Subdomains not working with domains containing wildcard

TomBeh

New Pleskian
I've migrated from 9.x to a 10.4.4 server, and have the following problem.

I have a domain with a wildcard, CNAMED to an application server elsewhere. *.example.com CNAME live.app.com

Originally the subdomains were A records in the single DNS zone. The problem is that now subdomains have their own DNS zone, the wildcard in the primary zone's master domain takes precedence. And I can't add the subdomain to the main DNS zone as it conflicts.

All the other solutions I can find to this are to do with ordering domains for catch all using Apache Vhost ordering, not using a wildcard DNS record. The apache solution won't work here as the wildcard domain (lower priority than subdomains) is hosted on a different server.

Any way around this? I'm almost at the point of giving up and moving the affected subdomains to another domain that doesn't have a wildcard. But that's going to cause lots of problems and work in itself. Is there a way back to the original single zone method for this domain?
 
Back
Top