cprapid.com is breaching privacy

laraaj

Registered
Nov 15, 2017
3
1
3
USA
cPanel Access Level
Root Administrator
Our company has 3 servers on each one of those server we added an account for our main domain for example maindomain.com so we can be able to manage
the hostname records and name servers records in a proper DNS zone, although only one of those servers is actually actively managing the live records for all 3 servers.

for example the first server let's call it server1.maindomain.com has a DNS zone maindomain.com with the following records :

server1.maindomain.com ====> "IP of the first server" # This is the hostname record of the first server
server2.maindomain.com ====> "IP of the second server" # This is the hostname record of the second server
server3.maindomain.com ====> "IP of the third server" # This is the hostname record of the third server

ns1.maindomain.com ====> "IP of the first server" # This is the name server record of the first server
ns2.maindomain.com ====> "IP of the first server" # This is the name server record of the first server
ns3.maindomain.com ====> "IP of the second server" # This is the name server record of the second server
ns4.maindomain.com ====> "IP of the second server" # This is the name server record of the second server
ns5.maindomain.com ====> "IP of the third server" # This is the name server record of the third server
ns6.maindomain.com ====> "IP of the third server" # This is the name server record of the third server

along with those records there is also the necessary NS records and the MX records are pointing to Google Gsuite.

the second server has the same records, while the third server which we just setup lately had default MX record.
The domain name "maindomain.com" Name Servers are setup using ns1.maindomain.com and ns2.maindomain.com
and there is not DNS synchronization setup between the three servers.

although the DNS is managed by the first server but some how the missed up MX record on the third server was affecting
our email and causing bounce backs, when customers try to send emails to "maindomain.com" which has it's emails hosted
with Google Gsuite. the sending servers end up trying to send emails through the third server.

the only explanation that makes it possible for you to allow all your customers to use ns1.cprapid.com and ns2.cprapid.com
as their domains Name Servers to point them to their Cpanel servers is that you synchronize all their DNS zones to your
own servers and that the servers "ns1cprapid.com" and "ns2.cprapid.com" are actually DNS servers which hosts all your
customers DNS zones without their permission even the ones that don't choose to use the Name Servers "ns1cprapid.com"
and "ns2.cprapid.com", which is a clear invasion of privacy.

worse than all is that there is some bug or mix up that some how you populate those DNS records to other DNS servers
which end up causing confusion and malfunctions in DNS domains that are not even managed by Cpanel.

to confirm that theory we even end up moving our DNS records to our registrar's internal DNS manager and we were still
getting the bounce back emails. only when we noticed that the error message mentioned the third server that we checked
and we noticed the MX record wasn't set to remote server. here is the bounce back message :


Reported error:550 5.7.368 Remote server returned authentication required to relay -> 550 Please turn on SMTP Authentication in your mail client. ;mail-db8eur05hn2200.outbound.protection.outlook.com;(EUR05-DB8-obe.outbound.protection.outlook.com) [52.100.20.200]:26592 is;not permitted to relay through this server without authentication.
DSN generated by:DB8P192MB0630.EURP192.PROD.OUTLOOK.COM
Remote server:"server3.maindomain.com"



Please fix this issue and stop synchronizing our DNS zones to your servers.
 
Last edited:

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
9,904
1,541
313
cPanel Access Level
Root Administrator
Hey there! ns1 and ns2.cprapid.com do not exist in the DNS system. You can check this with a dig or ping and you'll see they do not resolve:

Code:
$ dig +short ns1.cprapid.com
$ dig +short ns2.cprapid.com
$
cPanel has never offered nameservers for use with the cPanel & WHM product, and we absolutely do not sync any customer data to our own machines.

The "cprapid" domain is something we've recently implemented to allow users to have secure access to WHM right from the initial installation of cPanel & WHM on the server, instead of having to click through the SSL security warnings due to a self-signed certifcate. You can find more details on this here:


The most likely explanation for the behavior you're seeing is that the hostname was still set to the default, which is why the bouncebacks mention a "cprapid" domain.