I’ve seen some feeds on this but I didn’t see an exact sample.
Mind you I’ve set this up with Siteground and other hosts flawlessly, I set up the site with the domain and Cloudflare pulls in the DNS and MX records perfect after I switch the name records (never with a GoDaddy domain).
I took that process changing the name server with Godaddy after I auto pulled the websites records and the IP address didn’t match what was in Cloudflare when I looked up the DNS. The Cloudflare IP started with a 23. (proxied) and on the DNS lookup started with a 103.
Like I said I’ve done this 100 times and never have seen it. Any ideas?
FYI, I switched the name servers back to GoDaddy for just the sake of not having issues with the site.
Thanks ahead of time.
Update the correct IP did match in Cloudflare to what was at GoDaddy now I switched the Nameservers back to GoDaddy.
Glad to help with this. So when you use the DNS scanning tool when you onboard your zone to Cloudflare the records are being copied correct? However when you switch your nameservers to godaddy they are not scanning the records correctly?
If you can provide more context in regard to this issue we will be happy to help. Also any you can share any DNS lookups you have done with reacting the zone name that would be helpful. So we can see what you are describing as well.
It’s a GoDaddy thing unless you pay $350 a month for a dedicated ip. Which is more reason GoDaddy is possibly one of the worst companies on the planet. Just to bleed their customers another way.
Please tell everyone you talk to, to move their domains and hosting away from this shill of a company.
I have been dealing with their poor customer service and bad hosting for 10+ years. SiteGround never an issue. Godaddy confirmed this, if you are not using their Name Servers they change the IP address. Thank you though.