Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare
-
I have the same issue on 25.07.1 after upgrading to 24.11.
As I am running pfSense on VM on proxmox it was easy for me to revert back and confirmed no issues with 24.11.
I didn't check if disabling gateway monitoring fixed the issue
-
M m80s referenced this topic on
-
Also with Cloudflare? With IPv6?
-
@stephenw10 said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:
Also with Cloudflare? With IPv6?
didn't try, should it work with it?
Is it something that it will be fixed btw? -
Yes, it will be fixed. We just need more info. Like: are you also using Cloudlfare? Or is this something affecting multiple dyndns providers?
It should work with IPv6, yes, but there was at least on report of that failing specifically on Cloudflare.
-
...and freedns... and hetzner... and hurricane electrics is failing too with ipv6.....
-
Ah, that's good info. Ok...
-
@stephenw10 in my case I tried with 25.07.1:
- DuckDNS
- DeSec
both with IPv4 and both failing.
No issue on 24.11.Now i reverted back to 24.11 so I can't make further tests
-
@m80s said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:
DuckDNS
I'm running 25.07.1 and duckdns is working for me.
-
@m80s said in Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare:
@stephenw10 in my case I tried with 25.07.1:
DuckDNS DeSecboth with IPv4 and both failing.
Yeah that's unexpected. Unless they are using a WAN with a gateway that shows as down. In which case you would be hitting the new behaviour requiring gateway monitoring be corrected.
-
tried again with 25.07.01 and confirmed I need to set Disable Gateway Monitoring Action to make it work.
I think this behavior should be fixed
-
Well that's not a bug if the gateways used were marked as down. That's the expected behaviour in 2.8.X.
If the gateway being marked down is a change since 2.7.2 that could be a separate problem.
