Enable Domain Parking via WHM?

[FengYun]

Newbie Question....

Sorry about this Newbie Question....
Have not really posting anything here^^ Think this will be my first post

Lately Due to a request make by one of our VIP Client, we got no choice but to enable Domain Parking(Parked Domains), and since this our first time, we need some advice and also to secure risk we be taking?


Over at the user side(user cpanel), we have enable as follow. Will these be enought?
Parked Domains = 1
Addon Domains = 1



Then Over at the WHM side, what is the correct way to enable this function?

- Allow users to Park/Addon Domains on top of domains owned by other users. (probably a bad idea)
- Allow Creation of Parked/Addon Domains that resolve to other servers (i.e. domain transfers) [This can be a major security problem. If you must have it enabled, be sure to not allow users to park common internet domains.]
- Allow Creation of Parked/Addon Domains that are not registered

It is because we got the follwoing error, if either of the above option is not enable. Any advice? (True IP have been mask out)

There was a problem creating the parked domain. Show Details

Error from park wrapper: Using nameservers with the following IPs: 69.7?.XXX.YYY, 69.7?.XXX.YYY 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.

Btw, how come i have the above error, As i have configure/edit the correct DNS to this 2nd(or park domain)

For Example
www.domain.net ---Be park ontop of ---> www.domain.com



Many Thanks
Feng aka Crusnik

[JPC-Shaun]

Hi;

Please use the following options in the Tweak Settings for WHM.
This setup is based on security, performance and the most recomended setup.

Untick: Allow users to Park/Addon Domains on top of domains owned by other users.

Untick: Allow Creation of Parked/Addon Domains that are not registered

Tick: Prevent users from parking/adding on common internet domains


For the error message , Most probably you were trying to add the domain as an addon domain. cPanel will not allow it if the domain is not pointing to the correct Nameservers that are setup on the server. In order to setup this domain, please create a subdomain from cPanel and then park the addon on top of this from the WHM >> Park a domain option.

If there is any problem making the addon domain then it would be more appropriate to open a support ticket.

[JPC-NickO]

Hi,

As far as I am aware there is no real security risk in allowing parked domains.

[FengYun]

Hi,

Thanks for the fast reply
Well, since this the first time we enable this domain parking, we still like to based on security, performance and the most recomended way any webhosting solution will do. We are just a worry Newbie.........


Currently we have done the following

Untick: Allow users to Park/Addon Domains on top of domains owned by other users.

Tick: Allow Creation of Parked/Addon Domains that resolve to other servers (i.e. domain transfers) [This can be a major security problem. If you must have it enabled, be sure to not allow users to park common internet domains.]

Untick: Allow Creation of Parked/Addon Domains that are not registered

Tick: Prevent users from parking/adding on common internet domains

This one i highlight above in blue, is this correct way to enable parking? (cos we kind of worry about that warring message) We have tested so far, and this is working. We do not need to create a subdomain from cPanel then do the domain parking. With this, i can just do the parking rigth away, either in user cpanel or right at the WHM >> Park a domain option.


While doing this, the 2nd Domain nameservers is remain unchanged (it have been pointing to the correct NS all the time, More then 24-36hrs already) The Parking work until i enable the check in "Blue"


Can i also take this time to ask, why do i get the following error mesage? It is because, i kind of lost/dont really get to understand this error? Is it true Cpanel really stop us from to add the domain as an addon domain??

Error from park wrapper: Using nameservers with the following IPs: 69.7?.XXX.YYY, 69.7?.XXX.YYY Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers................................. ........

Many Thanks
Feng aka Crusnik

[JPC-Shaun]

Hi;

When a user adds a domain to their account, an authoritative entry for that domain is created on the shared hosts DNS server. This usually includes an MX record for the domain which directs mail traffic to the shared hosts mail server.

Theoretically the primary nameservers for the domain should be set to the shared hosts DNS server, and the shared hosts DNS should only be consulted regarding the domain if this is the case.

However if the shared hosts internal systems utilize the shared hosts DNS server for name lookups, the server will respond as if it was authoritative for the domain regardless of whether it is actually configured as the primary NS. This may lead to the internal systems receiving results that are inconsistent with the global DNS state.

One approach to avoiding this is to ensure a user cannot add a domain that is not already configured with the correct primary NS. In cPanel this is done by ensuring the following configurable parameters are disabled:

Allow Creation of Parked/Addon Domains that resolve to other
servers.

Allow Creation of Parked/Addon Domains that are not registered

Allow users to Park/Addon Domains on top of domains owned by other
users.

Also don't forget to check/Enable the option

Prevent users from parking/adding on common Internet domains (ie hotmail.com, aol.com).

For the error message you are experiencing at your end please open a ticket in the support department so that we shall investigate it and asssit you more efficiently.

[FengYun]

Hi,

Thinks you for the nice information, really help me alot on understanding how cpanel work. Anyway we manage to fix the problem. The hint is at this >>>

/etc/ips.remotedns and make the proper A entries on that remote nameserver.

My partner manage to review and make some changes coz we do did some customize to our vps. Over all what he have done, he did not tell me, but the above is what he told me.



Thanks for the support

Cheer

[JPC-Shaun]

You are welcome.