Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare
-
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.
-
@stephenw10 Hello i am not sure to understand the workaround or the solution.
I just update from 2.7.X to 2.8.1 and Dyndns doesn't show IP on dashboard (N/A and time)
- IP string is correctly showed on diag php command
- checkip.dyndns.org is OK
- i create an additonnal checkipservice on my website to be sure
What we must do step by step to fix this problem please.
Thanks
regards -
Are you running it on an interface that has a gateway shown as down? If so change the target to something that responds or set it to unmonitored.
-
@stephenw10 Hello, It appears that the gateway was indeed listed as offline because originally it was using the internet provider's gateway IP address, and the provider had blocked ICMP ping requests. Therefore, you simply need to enter a reliable IP address that accepts ICMP pings, such as 8.8.8.8, 8.8.4.4, 1.1.1.1, etc.
Check gateway:
Stats -> Gateways
Check if Gateways is marked offline (red)Put a realiable IP to check 'online availability':
System -> Routing -> Gateways
Click on little pencil to gateways and change Monitored IP field with 8.8.8.8 or 8.8.4.4 or any other Ip that you known which can be pinged 24/24 - 7/7
Your gateways will be properly checked to determine if they are online or not.This way you don't disable anything, you actually improve your configuration :)
I hope this can help others. Thank you @stephenw10
