cPanel uses a system of verifying someone owns a domain name by checking it's nameservers before allowing that domain name to be added as an addon domain in the user's cPanel. I understand the policy for this. It's meant to insure that users don't just add random domains to their account that they have no control of. Think of if someone added hotmail.com as an addon domain to their account - they could then steal all mail sent from that server to @hotmail.com email addresses. (Although to be clear, hotmail.com is popular enough that it's prevented through a separate common domain list).
But what do you do in instances where a domain name cannot be registered and set to specific nameservers unless those nameservers return a valid DNS zone? This results in an endless loop of failures:
Domain cannot be added to the cPanel account because the domain is not using the server's nameservers.
Domain cannot be set to server's nameservers because no DNS zone exists for domain on those nameservers.
What is the recommended workaround for this scenario?
I suppose enabling:
Allow Unregistered Domains
Allow Remote Domains
would be options - although less than ideal.
But what do you do in instances where a domain name cannot be registered and set to specific nameservers unless those nameservers return a valid DNS zone? This results in an endless loop of failures:
Domain cannot be added to the cPanel account because the domain is not using the server's nameservers.
Domain cannot be set to server's nameservers because no DNS zone exists for domain on those nameservers.
What is the recommended workaround for this scenario?
I suppose enabling:
Allow Unregistered Domains
Allow Remote Domains
would be options - although less than ideal.