Addon domain forcing me to update nameservers before I want to..??

[angelleye]

I've got a fresh account created in WHM. I loaded cPanel for this account and attempted to create an Addon Domain, but I'm getting the following message:

Error from park wrapper: Using nameservers with the following IPs: 65.61.188.4,69.20.95.4 Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver.

I don't want to update the nameservers for this domain, though, until I've gotten all of the data, site files etc. moved over and have fully tested the site on the new server.

Why is it forcing this? It won't even let me create the addon domain. I don't seem to have this problem with a new account in general.

Any information on how I can get around this would be greatly appreciated. Thanks!

 

[ruzbehraja]

This is a security measure.

To allow the addon domain to be created:

Go to WHM >> Tweak Settings >> Allow Remote Domains >> Select ON.


Remote Domains ON will:
"Allow creation of parked/addon domains that resolve to other servers (e.g. domain transfers) This can be a major security problem. If you must have it enabled, be sure not to allow users to park common Internet domains."

 

[angelleye]

Thanks for the info!

Can you explain why this would be a security risk? I've always done things that way and I guess I just never had a server that blocked me from it before.

I just want to create the addon domain and get it all up and running, tested, etc. prior to updating my nameservers. I generally just update my local hosts file so my machine points to the new server IP when I use the domain accordingly. This allows me to fully test everything prior to making it official by updating the nameservers.

Is there some other procedure I should be following for such migrations?

 

[ruzbehraja]

If multiple dummy domains are added, and the Mail Exchanger is set to Local, all users on that server, sending out genuine mail to the genuine domains, will actually be sending it out to the dummy accounts on the server.

Example:

If I create yahoo.com, as an addon domain / cpanel account,
and then setup a dummy email account [email protected],
other users on the server, who send a mail to the real [email protected],
will actually be sending it locally to the dummy account on the server.

This can be a major security issue and can lead to impersonation and fraud.

Hence, the options in WHM >> Tweak Settings to:
- Allow unregistered domains
- Block common domain usage
- Allow Remote Domains

Tweak Settings

I dont think there is any other reason, although others maybe able to shed some more light on it.

As far as the migration of accounts is concerned, you maybe right. I also do not do it differently, due to convenience.

But I didnt understand the hosts file part of it? Hosts file on your local machine or the old server which you have migrated from?

Maybe inputs from others will be useful.

 

[angelleye]

Ok, thanks for the info!