SOLVED Add-on domain query

[chanlon1]

Hoping someone can advise on what should be relatively simple concept.
I have a working domain pointing to a folder on a server.
Eg. domain.com will point to serverA

I am now looking to move to ServerB.

I would like to set up the folders and files etc on ServerB, get it all working, and then finally change the Nameservers to point to the ServerB.

On ServerB Cpanel, When I try to use the Add-on Domain feature, it returns "This domain points to an IP address that does not use the DNS servers associated with this server. Transfer the domain to this server’s nameservers at the domain’s registrar or update your system to recognize the current DNS servers. To do this, use WHM’s Configure Remote Service IPs interface."

Is it just as simple as adding in the existing NameServer IP's into WHM and then I can use the Add-on feature and get the data set up?
If so, is it correct to say that the existing domain will still work okay?
After everything is transferred over, do I need to remove the Remote Service IP's I added, or do they need left?

I know I could probably do all the above by just creating my own folder on ServerB, and then moving it into the Add-on folder when its created, but curious about the above.

Many thanks.

 

[kodeslogic]

This is a common issue while adding Addon domains in cPanel.

You can simply solve this error from your WHM panel. There is an option called “Allow Remote Domains” in WHM tweak settings.

Switch ON the option “Allow Remote Domains” to add new Addon domains that having name servers other than your server. Follow these steps to enable it.
Do follow these steps

1. Log into WHM panel as root user.
2. Go to Tweak Settings
3. Search for “Allow Remote Domains”
4. Turn ON and save.

As per your profile information, you have cPanel Access Level: Root so you'll be able to make the above changes.

After these changes, you will be able to add domains that are already pointing to the old server, when your migration is complete you can verify your data integrity and then change your Nameservers to point to your new server.

 

[chanlon1]

Many thanks for the reply. I wasn’t fully aware of that WHM option and I can see it now.
thanks.

 

[kodeslogic]

I'm glad that it helped to resolve your problem.

 

[chanlon1]

I'm glad that it helped to resolve your problem.

So I am getting there.
I got the add-on domain added into the new server.
Placed a simple index.html file there.
Updated the nameservers to point to the new server.
After the propagation occurred, when I go to a browser and enter my domain URL, for example: domain.com, what it is trying to resolve to is https://domain.com/domain.com/

If I change to just https:// domain.com/ then my new index.html file appears.

Any ideas why the duplication in the URL?

 

[kodeslogic]

If I change to just https:// domain.com/ then my new index.html file appears.

Do you mean you have to manually add https:// in your browser to access the new index.html file?

 

[chanlon1]

Do you mean you have to manually add https:// in your browser to access the new index.html file?

Regardless if http or https it was happening. However, I think I got it sorted as the subdomain wasn’t 100%. Once I got it sorted out all seem to be okay now.

 

[cPRex]

Glad you were able to get things working well!

We have an article with additional details about how you can work around that DNS error you encountered earlier if you'd like to check that out: This domain points to an IP address that does not use the DNS servers associated with this server.