Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare
-
Ok. It may still be the issue though as the pppoe code was changed to allow both connection types.
-
@stephenw10 Just configured another DynDNS Service and switched to the new if_pppoe kernel module. The problem is still there
-
Only after switching to if_pppoe?
Which interface are you using pppoe on? The actual 'wan' interface?
-
@stephenw10 before and after switching. Just wanted to confirm that the new if_pppoe module is not the culprit.
I am using the 'wan' interface -
Hello.
I am experiencing the same faulty behavior.
When debugging the PHP-Command in pfSense, it returns an IPv6 in my case. -
When querying
pppoe0? -
@stephenw10
Yes.
Still quite common in Germany. (V)DSL so it's based on pppoe.Dynamic DNS updates stopped working just as 2.8.0 was installed. Quite a bummer for me because I am heavily depended on that function.
I also tested it with the old pppoe driver and the new one - same behavior, despite I am not using cloudflare. -
Do you only have an IPv6 address there?
I'm using PPPoE over VDSL here and it work fine. There must be something else in play.
-
Is your upstream gateway shown as online?
In 2.8.0 (and 25.03) dyndns update will fail if the gateway is offline.
-
@stephenw10
Nope, it's dual stack (IPv4 and IPv6) -
@stephenw10
It's indeed offline.
I just changed it to unmonitored and, who would have thought, the DynDNS update is working again. -
@djstone
ok, I'll have to correct that statement - IPv6 worked. IPv4 shows "0.0.0.0" as IP. -
@djstone
I think the cause for the IPv4 address not updating might be, that I already did it via another service. Will restart the pppoe connection and see if it comes back to live correctly. -
Ok, so far the gateway status seems to have been the root cause. Thank you for your fast response.
It would be nice, if one checks "verbose" on the Dynamic DNS configuration, to actually receive a verbose ouput or at least a hint to why the update failed.Last thing I see me having to do is dig into the php source code to find the possible causes.
Thanks again. -
Yup I agree. Let me see about adding some debugging there.
-
Thank you @stephenw10. That worked for me also.
-
Is there any news about the problem, or is there a workaround?
-
Trying to follow along, not tried everything you guys did but found this post and that worked for me.
Turned of Gateway monitoring only and Dynamic DNS became online at once after a force refresh.
https://www.reddit.com/r/PFSENSE/comments/1kngpej/ddns_using_cloudflare_stopped_working_after/
-
@TheBigS try to check the option. For me worked
-
Yup the change of behaviour here is that the client checks the WAN is up by the gateway status on it before it tries to update. So if your gateway monitoring shows as offline the best solution here is to correct that so it's pinging something that responds. An alternative is to just mark the gateway as always up so it doesn't get monitored but then you lose gateway data.
