Mirroring Reddit thread here - https://www.reddit.com/r/opnsense/comments/1rmqih8/opnsense_setting_wrong_address_with_native/
Since maybe 1-2 weeks ago (upgraded to 26.1.3) by DDNS client suddenly changed my external IP to 104.18.0.0
I've used cloudflare-ipv4 "Check ip method"
104.18.0.0 - belongs to Cloudflare
Switching to Akamai fixes the problem
Hi,
we've been experiencing the same issue for a few days now on multiple firewalls running the latest firmware. Switching to "icanhazip" didn't resolve the problem. I'm going to give Akamai a try
Does anyone have an idea what might be causing this?
Quote from: NeoV00 on March 17, 2026, 03:18:36 PMDoes anyone have an idea what might be causing this?
The Cloudflare endpoint https://1.1.1.1/cdn-cgi/trace is broken.
Switching to akamai-ipv4 works for me as a workaround.
FWIW, opening https://1.1.1.1/cdn-cgi/trace shows my correct IPv4.
Cheers,
Franco
I also get 104.18.0.0 at https://1.1.1.1/cdn-cgi/trace
Not using opnsense
Oh, thanks it's not only me...
This drives me crazy since a week or so. Without updated DNS I am locked out of my home network. In my case, I regulary update
- IPv4 of sub1.domain.com
- IPv6 of sub1.domain.com
- IPv4 of sub2.domain.com
I thought it was somehow related to having three entries and tried to isolate it to one of them, but no success.
The weird part is:
- sometimes it works
- OPNsense even adopts the wrong IP, i.e. cloudflare is confirming 104.18.0.0 back to OPNsense. But only once the correct was updated to cloudflare.
I updated the IP once via the API call directly (outside OPNsense) that seem to have worked, but maybe it was just coincidence
Edit: Understood, the "check ip method" used cloudflare to determine the ip address and that thing is broken
Same happened to me, thanks for posting about this.
I chose akamai now and things work again.