Our credit card processor is asking for the IP (vs FQDN) where transactions originate so as to whitelist it. I am not sure as to how often cloudflare changes the dynamically allocated IP but what is certain is that nslookup returns two IP’s - which seems more than what the CC processor can handle
Is there a workaround allowing for a single and static IP on rDNS?
My understanding is that for all practical purposes, unless I specifically browsed to my IP, traffic to/from my FQDN was channeled through cloudflare, so that when browsing (or ordering a purchase) on my FQDN, the visible IP is cloudfalre’s - am I mistaken?
My server’s IP will not work but that is to be expected: anything that was not whitelisted on the CC processor’s side will be rejected - and they specifically asked for the FQDN and IP - I gave one of the two cloudflare’s IP showing up on nslookup since they dont allow more than 1 IP
Next steps is indeed to give server’s IP, but I would still like to know if my understanding of how cloudflare IP get in the mix - in case my server’s IP does not work and they somehow look for a match between FQDN and rDNS