Hi friends, my customers use cPanel to run WordPress on subdomains of my main domain, so https://[bob].example.com. This works great. We don't need/use DNS or email.
Some customers want to take their own pre-existing domain "www.example.net" and map it onto the top of the cPanel/WordPress instance I've given them.
When I set this up in cPanel -- either as a Parked Domain, Addon Domain, or Alias -- cPanel decides that is the DNS authority for example.net (it's not!) and creates a full DNS zone file. For the most part we can all just ignore this *except* when WordPress wants to send an email to [email protected]... now cPanel's mail server locally delivers it to some unmonitored garbage account.
Is there really no way to configure cPanel to answer on a particular hostname without creating a bunch of unwanted DNS records? (It should be just one line in the httpd conf files right?) In an ideal world I would like that httpd conf file line but I'd also like to take advantage of the AutoSSL feature too.
If cPanel internally requires zone files to be created, then I guess I could park the remote domain on my cPanel and then lookup the real MX records and replicate them in cPanel's DNS, and even do a nightly job to keep these in sync... would that be the most practical way forward?
If there's some conf file of remote domains that will allow cPanel to mostly work but not actually create the DNS zone files, that would be really helpful. I only have about 10 of these customers and I'm ok setting things up manually for them, but right now the lack of email from their WordPress instances is a big problem & they may leave because of it.
Some customers want to take their own pre-existing domain "www.example.net" and map it onto the top of the cPanel/WordPress instance I've given them.
When I set this up in cPanel -- either as a Parked Domain, Addon Domain, or Alias -- cPanel decides that is the DNS authority for example.net (it's not!) and creates a full DNS zone file. For the most part we can all just ignore this *except* when WordPress wants to send an email to [email protected]... now cPanel's mail server locally delivers it to some unmonitored garbage account.
Is there really no way to configure cPanel to answer on a particular hostname without creating a bunch of unwanted DNS records? (It should be just one line in the httpd conf files right?) In an ideal world I would like that httpd conf file line but I'd also like to take advantage of the AutoSSL feature too.
If cPanel internally requires zone files to be created, then I guess I could park the remote domain on my cPanel and then lookup the real MX records and replicate them in cPanel's DNS, and even do a nightly job to keep these in sync... would that be the most practical way forward?
If there's some conf file of remote domains that will allow cPanel to mostly work but not actually create the DNS zone files, that would be really helpful. I only have about 10 of these customers and I'm ok setting things up manually for them, but right now the lack of email from their WordPress instances is a big problem & they may leave because of it.
Last edited by a moderator: