There's a site "mydomain.com" that is currently being hosted on GoDaddy. GoDaddy is also providing the DNS services for this domain.
We're trying to migrate the site over to my cPanel based server as a 'namebased' account. DNS services will continue to be provided by GoDaddy.
In order to have a smooth transition, we want to point a subdomain to the namebased account on my server initially, and then when everything is confirmed 'running-smoothly', point the main domains to it as well.
On the GoDaddy DNS, I created an A record for 'new.mydomain.com' and pointed it to the IP address of my cPanel server 123.45.6.7. This IP address is currently working for several other namebased accounts I had previously installed on the same server. ('other-domains.com', etc.)
I left the IP address associated with 'mydomain.com' (A record) as it was, pointing to the already running site. Thus 'mydomain.com', 'www.mydomain.com' still all point to the running GoDaddy hosted site.
On my cPanel server, I created an account for 'mydomain.com' as eventually, we would want to point the entire domain to it rather than just 'new.mydomain.com'. I added a subdomain to that new account for 'new.mydomain.com' as well.
So on the cPanel server, Domain = "mydomain.com" and there's a SubDomain defined for it as "new.mydomain.com"
I can confirm that 'new.mydomain.com' has propagated to 123.45.6.7
However, when I go to 'new.mydomain.com' I get the "Sorry!" cpanel page can can see that the URL has been redirected to 'new.mydomain.com/cgi-sys/defaultwebpage.cgi'
I've done this 'point-a-temp-sub-domain' method a couple times in the past and it worked smoothly, but for some reason it's not working for me this time. Not sure where I went wrong. I've looked as the settings of some other workin namebased sites on my server as well as DNS records I control on GoDaddy that are correctly pointing to said namebased sites and they seem to be set up the same a my new problem 'new.mydomain.com' site.
I'm not sure where to look on my cPanel server to dig deeper into this error, or if I need to change something on how I defined the site to begin with to fix this problem.
Thank you in advance for any help or hints you can provide.
We're trying to migrate the site over to my cPanel based server as a 'namebased' account. DNS services will continue to be provided by GoDaddy.
In order to have a smooth transition, we want to point a subdomain to the namebased account on my server initially, and then when everything is confirmed 'running-smoothly', point the main domains to it as well.
On the GoDaddy DNS, I created an A record for 'new.mydomain.com' and pointed it to the IP address of my cPanel server 123.45.6.7. This IP address is currently working for several other namebased accounts I had previously installed on the same server. ('other-domains.com', etc.)
I left the IP address associated with 'mydomain.com' (A record) as it was, pointing to the already running site. Thus 'mydomain.com', 'www.mydomain.com' still all point to the running GoDaddy hosted site.
On my cPanel server, I created an account for 'mydomain.com' as eventually, we would want to point the entire domain to it rather than just 'new.mydomain.com'. I added a subdomain to that new account for 'new.mydomain.com' as well.
So on the cPanel server, Domain = "mydomain.com" and there's a SubDomain defined for it as "new.mydomain.com"
I can confirm that 'new.mydomain.com' has propagated to 123.45.6.7
However, when I go to 'new.mydomain.com' I get the "Sorry!" cpanel page can can see that the URL has been redirected to 'new.mydomain.com/cgi-sys/defaultwebpage.cgi'
I've done this 'point-a-temp-sub-domain' method a couple times in the past and it worked smoothly, but for some reason it's not working for me this time. Not sure where I went wrong. I've looked as the settings of some other workin namebased sites on my server as well as DNS records I control on GoDaddy that are correctly pointing to said namebased sites and they seem to be set up the same a my new problem 'new.mydomain.com' site.
I'm not sure where to look on my cPanel server to dig deeper into this error, or if I need to change something on how I defined the site to begin with to fix this problem.
Thank you in advance for any help or hints you can provide.