Addon Domain, Point to different server

[joedevil]

Hi, I have a cpanel reseller account, and I have a customer how has 2 domains.

The main Domain is hosted on our server, the other domain is currently hosted at another server with a different host.

Our customer has alot of files on that other server so they don't want to do a complete move right away as they had many sub domains associated with that domain, so they want to point the domain to our name server, and point the main site and it's old sub domains to their proper ip's that are associated with the other host.

How can they do this on their own? We added the second domain as an addon domain, and modify the DNS, for
domain2.com A OLDHOSTIP
sub1.domain2.com A OLDHOSTIP

does not work as they never propagate and keep pointing to the new server ip (our host)

I don't have shell access in my reseller account either so I can't exactly SHELL and modify TLD files, what are my options. I am fairly new to cpanel.

 

[mtylerb]

Where is the registrar pointing the domain2.com to? Your nameservers or the oldhost nameservers? I believe they should be pointing to the latter if you want to keep the site files over there.

Sorry, I just re-read, you want subdomains of domain2 pointing to one IP and domain2 pointing to the new IP?

 

[joedevil]

Where is the registrar pointing the domain2.com to? Your nameservers or the oldhost nameservers? I believe they should be pointing to the latter if you want to keep the site files over there.

Sorry, I just re-read, you want subdomains of domain2 pointing to one IP and domain2 pointing to the new IP?

Maybe I mis spoke.

Client has the following:

Domain1.com : our host
sub1.domain1.com : our host
sub2.domain1.com : our host
-------------------------------
Client wants to add domain2.com
it's pointed to our name server. and they want to setup a records like this.

domain2.com : oldhost ip1
sub1.domain2.com : oldhost ip2
sub2.domain2.com : oldhost ip3
sub3.domain2.com : oldhost ip1

---------------------------------------

I want to avoid having to provide a second Cpanel since I am limited to 200Cpanels, essentially we would act as a DNS until they moved their files. They want to avoid as much down time as possible during the transition.

 

[mtylerb]

Would it not make sense, then, to point the registrar of the domain to the oldhost nameservers while they transfer the files over to the new one? Then once everything is up, set the new nameservers (yours) into the registrar. That's what I did recently and had a total of an hour downtime while I transferred the database over. You can run both sites concurrently so when the propagation is happening, it will have little to no downtime.

 

[joedevil]

Would it not make sense, then, to point the registrar of the domain to the oldhost nameservers while they transfer the files over to the new one? Then once everything is up, set the new nameservers (yours) into the registrar. That's what I did recently and had a total of an hour downtime while I transferred the database over. You can run both sites concurrently so when the propagation is happening, it will have little to no downtime.

Some of their subdomains for domain2.com will still need to point to the old server, they are not moving their SVN for their projects as that is setup on a dedicated box. So regardless I still need away of having multi ip's across addon domains.