Even tho i set the dns settings to point out to my server’s ip address which is 148., when i curl the url i see the ip addresses starting with 104. and these I assume is tied to cloudflare but actually that’s not my server’s ip address, so that I need to quickly resolve this issue as updating the records didn’t help
What steps have you taken to resolve the issue?
I updated dns records over and over again, utilized cloudflared tunnel on my server which works but dns names are misconfigured so that when use the command ( dig ibmziue.com +short ) it just lists numerous ip addresses from cloudflare but not the one that I registered to A AAAA CNAME records. Which just doesn’t make any efffect and change has been made a week ago. The site is currently reachable with explicit ip address
What feature, service or problem is this related to?
I just don’t understand the issue, I setup cloudflared on my mainframe which does have s390x architecture so I compiled from source but works perfectly fine, the environment that the mainframe is in does not allow 443 or standardized other ports so i am using 8081 but explicitly configured that on tunnel settings and apart from that properly applied page rules. The apache on the server side works just fine and I setup certificates perfectly fine and I verified them. The SSL/TLS configuration is on “Full” and then i just directly type "https://my_server_ip:8081 i can reach it out perfectly fine even I get this site is not safe , and I choose advanced option and choose proceed. So the site does work perfectly fine and functional but what I’ve done regards to the url to work, did not work as all I can say. The A and AAAA records are properly configurated like a week ago also . Sicne the environment that the mainframe is in blocks UDP, i disabled the the QUIC/UDP and I am just using TCP right now. It’s just weird and I couldn’t figure out the issue. I recreated the tunnel numerous times and I tried many many times which just didn’t work. So I really need assistance. Thanks!
) records.