GoWilkes

Well-Known Member
Sep 26, 2006
439
8
168
cPanel Access Level
Root Administrator
I have an account set up on WHM for a .CO domain, and I have 100+ other domains parked on top of it. I never market the .CO, though, so it's mainly just been for internal usage.

I was recently able to buy the .NET version of my domain, and I would like to set it up to be the main domain for the account and park the .co on top of it. Then next year I can just let the .co go.

Is there an easy way to change the main domain for the account? Or am I going to have to create a new account manually and then move all of the parked domains?
 

GoWilkes

Well-Known Member
Sep 26, 2006
439
8
168
cPanel Access Level
Root Administrator
Just for clarity...

When I change the domain for the account and then park the original domain to the account, is there going to be any propagation time?

I'm 90% sure that the answer is no since the domains themselves won't be changing, but I wanted to make 100% sure before I risk any major down time!
 

GoWilkes

Well-Known Member
Sep 26, 2006
439
8
168
cPanel Access Level
Root Administrator
Sorry for bumping an old thread, but I'm just now getting around to doing this.

Can you guys let me know of any potential errors or pitfalls that I need to look for after making this change? My plan is to unpark the .NET from the .CO, then change the primary domain from the .CO to the .NET while unselecting "Rename prefixed databases and database users", then immediately parking the .CO on top of the .NET.

I'm pretty sure that I'll have to modify my email account usernames to the .NET (not a big deal), and all of the FTP accounts will need to change the Host to the .NET. Is there anything else I should check after changing it to make sure all is well?
 

cPanelMichael

Technical Support Community Manager
Staff member
Apr 11, 2011
47,910
2,233
363
cPanel Access Level
DataCenter Provider
Twitter
Hello @GoWilkes,

Here are some items to consider:

1. Read the the email account section of the document below for information about what happens when you remove and re-add an alias:


2. If you use PHP applications (e.g. WordPress), be mindful of any configuration settings or .htaccess rules that rely on specific domains. Here's an example of one potential issue:


3. Consider creating an example/testing account with similar configuration settings and data and perform the action on the testing account first. The following document is helpful if you want to avoid registering real domains for testing:


4. Always backup the account prior to making this type of change. This way, if something goes wrong, you can restore the account to it's earlier state.

If you encounter any problems, let us know.

Thanks!