Tell me more ×
Webmasters Stack Exchange is a question and answer site for pro webmasters. It's 100% free, no registration required.
up vote 0 down vote favorite

I'm trying to do an A record point to transfer the hosting of a domain from one provider to another. I don't want to change the nameservers as this will result in emails going down.

The output when I dig for the domain shows the correct IP (78.46.63.87) for the new host. I know A records can take a while to propagate but Its been over 36hrs now and I still keep getting this error(below) when I try to pull the domain through as an addon domain via Cpanel on the new host. Are the old nameservers conflicting with the A record point?

here's the error: Using nameservers with the following IPs: 208.80.125.4,208.80.126.4,208.80.124.4,208.94.148.4 Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver.

share|improve this question
I believe it wont make any conflict with your old provider. If you have pointed your A record to your new provider, the A record will point to new IP address. Have you ping the result? What is the result? Please make sure you have setup it correctly. :) – Mark Shawn Apr 30 '12 at 3:00
Could you tell us the hostname you're trying to transfer, and perhaps the names of the two hosting providers? (One of them is presumably Aegis Hosting, as that's where the reverse DNS for 78.46.63.87 points to, but what's the other one?) That would make it easier to tell what's going on. – Ilmari Karonen Jun 30 '12 at 13:54

2 Answers

up vote 0 down vote

You could transfer your email hosting to http://www.zoho.com which gives 3 free pop accounts. Once your MX records propagate which takes just a few minutes, go through the domain transfer with name servers and all as usual.

share|improve this answer
up vote 0 down vote

This can be fixed in an option in WHM. If you are on shared hosting and don't have access to WHM, contact your host.

WHM -> Tweak Settings -> Allow Remote Domains

Enabling that will fix it. I ran into this all the time when I worked in support for a hosting company.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.