Transfer Domain from Host to my Account

Currently our domain name management is hosted by our web developer on CloudFlare. Registrar is GoDaddy. We have a new webhost for our website. I would like to take over managing our name servers and keep them on CloudFlare. I found the following https://support.cloudflare.com/hc/en-us/articles/204615358-Moving-domains-between-Cloudflare-accounts

Is this all that is necessary? What does my current host need to change on CloudFlare? I thought this wold be simpler than export DNS records than reimporting them. Sorry for this question. I have not managed DNS for some time.

That really is the key part. If your dev can export the BIND file and hand it off to you, you can add that domain to a new account and import the BIND file.

Ok, there’s a second key part: Updating your Name Servers at GoDaddy. It’s pretty seamless as long as your DNS records are complete. And within 48 hours, all traffic will go through your new account.

So i was only able to get a csv file from my old developer. I added my domain and then used the automated feature to pull over the records. Almost all of the A, AAAA, and CNAME records came over as proxied. Would that mean under the old developer’s account, those entries were proxied? And I should leave them as is?

Oddly subdomains did not get pulled over automatically and I had to add those A records. Some I did not proxy (vpn, sftp, duo). seemed like the right thing to do. I saved my changes but have not made my changes at the registrar, GoDaddy.

DNS Import is a guessing game by Cloudflare, so it’s not a surprise that many subdomains weren’t guessed, as they’re often unique to a customer.

Mail-related hostnames should not be proxied. Rule of thumb: Proxy is only for HTTP/S traffic.

Things were looking good. i edited the dns recods and changed the NS records at godaddy. Now i have a error 1000 dns points to prohibited IP when i go to our website.
Greg

This error is most commonly caused by one or more DNS records in the Cloudflare dashboard pointing to a Cloudflare IP address. It can also be caused if your DNS record(s) reference another reverse proxy. To resolve this, you should edit your DNS records to point to your origin server’s IP address.

More details in this Community Tutorial:

And this support article:

1 Like

Would it be a problem with a cname record for the website.? Out of the records i was given it had a cname record of domainname.wpengine.com type www. The DNS app gives me this when i try and add it. An A, AAAA, or CNAME record with that host already exists. (Code: 81053)

CNAMEs are generally safe, but may need to be set to :grey: DNS Only.

But you can’t have a CNAME that duplicates an existing A/AAAA/CNAME hostname (first column of the DNS records list).

Thank you for the information. After cleaning up the records that were imported things cleared up. I appreciate your quick responses.

1 Like