• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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