Park domain in WHM uses up customers addon limit

[4u123]

I have searched for an answer to this but so far have come up with nothing.

Sceanrio...

1. Customer needs a domain parking onto an existing addon domain - this can only be done in WHM
2. I park the domain in WHM onto thier addon domain.
3. When the customer logs in to cpanel - their "addon domains" limit shows that they have used another addon when this is not the case.

This hasnt always been a problem but certainly has been happening for at least 6 months on all our servers.

[Ulysses]

1. Customer needs a domain parking onto an existing addon domain - this can only be done in WHM
2. I park the domain in WHM onto thier addon domain.
3. When the customer logs in to cpanel - their "addon domains" limit shows that they have used another addon when this is not the case.

We have the same problem, AND when the new domain is parked on the addon domain via WHM, the URL resolves to the addon domain - not the parked domain as it should.

Example: Park parkeddomain.com on addondomain.com via WHM and parkeddomain.com redirects to addondomain.com URL

[4u123]

Hi,

It doesnt redirect when I do it - the park works correctly but it still eats up one of the customers available addons. Its a real pain in the a$$

[nozzle]

I'd like to bump this to see if we can get a reply from one of the cPanel staff or guru's.

I have this same issure. One of my customers asked if this could be done (Park a domain on an Addon) and we told him yes. So he bought 5 domains to park on one of his addons only to have us find that the parks used up Addon slots.

We have tried using the WHM function as well as editing the apache config file directly to no avail. All methods seem to be picked up by cPanel and counted against his available Addons.

Is this a change of previous behavior?

What would be the correct/proper way to Park a domain on an Addon without having it count against the available Addons in the users control panel?