I have an A record pointed to one of our public IP addresses in CF DNS but when I ping or NSlookup it returns a very different address. I have verified that our primary domain has the correct nameservers setup for CF. I’ve tried proxy and DNS only settings on the record. I’m starting to feel pretty dumb. Please help!
When you are having Proxied (
) records, they will replace the IP addresses to the public with Cloudflare IP addresses, so that Cloudflare can protect and serve you.
You can move a record to Unproxied (
) / DNS-only, which will make the public see the actual IP address that you enter in the DNS dashboard, but doing so, will make any traffic flow directly to the server you have set there, and not over Cloudflare.
With Unproxied (), Cloudflare simply serves as a DNS provider, and you won’t have any kind of functionality that Cloudflare otherwise would be able to provides on top of your site.
Feel free to elaborate on more details (domain and record name, DNS settings, what you expect to see, …), if you would like us to dig deeper?
If you did actually try the DNS only option, you might not have waited enough for the previous DNS cache to expire.
2 Likes
Monitoring is the record
ipsglobal dot com is the domain
Right now it is set to DNS only and it fails.
When it was set to proxy it would return a Cloudflare IP instead of our public IP.
Returning a different IP address is the whole point of proxying. That’s how it works. People connecting to your address actually connect to Cloudflare, and Cloudflare sends the connection on to you.
I can look up that record, and it succeeds, and it’s not currently proxied. What is it you’re trying to accomplish?
3 Likes
It’s supposed to pull up a login page for an internal system. I think the problem is in our firewall config. I’ll be getting with our network guys in the morning.