Proxied but not proxied?
Hi all,
I'm looking for some general info but I dont' even know what to google here.
I have a client who has a www domain pointed with a Proxied A record, and when I do an NSlookup I see all the anycast addresses like I'd expect.
The Apex domain however, says it's proxied in the cloudflare portal but when I do an NSlookup on that domain I get the public IP of the origin server.
From what I understand, this might be a requriement for Axctive Directory DNS but I'm not sure what exactly is happening here. The client hardly knows their own DNS so they couldn't answer the question for me.
Can anyone think of what might be going on, or what I'm missing? The goal is to be able to launch a new website, but I want to have a good grip on their current traffic flows before we schedule a launch date.
3 Replies
what exactly are you looking up, can you share the domain name?
There's a few instances where proxied records would return origin IPs. For example, if the zone/website was still pending setup, or you paused Cloudflare on the overview page. It could also be revealed via svc records to other unproxied records
I think I just figured it out actually. Looks like the client uses AWS route 53 to point the naked domain to the backend server directly.
But that Route 53 record for www points to cloudflare, and cloudflare points to the origin servers
using cname setup?
would make sense why they have nothing on their apex if so