Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare
-
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.
-
@stephenw10 thanks a lot. my pfsense is now pinging quad9 and now everything is working.
-
...its the same here with pppoe and dhcp
using afraid, and hurricane electrics as ddns service.
but it's half bad, another reason why to abandon pfsense after nearly 18 years of usage.....
-
why in earth should I disable gateway monitoring since i have three pppoe connections and a dhcp connection which is a redundant setup for internet connection?!?
disabling gw monitoring is a very crude workaround for a problem which should not exist in the first place! Come on.... ddns is not rocket science!!!!
-
It seems as if it is the old problem from a couple of years ago coming back again:
whent you get an IPv6 Address via pppoe or dhcp you also get some link local addresses for that. somtimes even the default gw is link local.
It seems in some circumstances the ddns client of pfsense does not get the right ip address and makes a lot of silly stuff with the ll address....
because even if forcing the update and even when the given ipv6 address is the same as before it fails to "update" the ddns service and shows a cached "::" entry ....
I cannot say if the entry itself is getting updated, since, in my case, there is no change.....
BTW: I just encountered my 4 IPv6 WAN Adresses are totally mixed up in the ddns entries..... I don't recon any rule about how pfsense mangled it.... wan1 has ddns IP from wan3 wan 2 and 4 does not have any dyndns address. The addresses itself are correctly assigned to the correct interfaces in the interface section.
-
Ok so the issue you're seeing is only affecting IPv6 addresses?
And gateway monitoring is working fine for those IPv6 interfaces?
That seems separate to the issue other users here were hitting.
-
The IPv6 Addresses are not updated in the DNS. I checked that.
Why should that be another Issue? Gateway monitoring for itself is working fine as far as I can tell right now.
The ddns script does not resolve the current IPv6 Address - totaly irrelevant if I use a script or not - in the status display it is always "::" and not a current or past IPv6 Address.
-
Right, it's just that this seems to be a new/different issue to that which was discussed in this thread. Which was that a change in the behaviour of the dyndns update script meant it would not run against a WAN where the gateway is marked down.
As I understand it that's not what youre seeing? -
I just installed 2.8.0 and was having difficulties getting Dynamic DNS to work with Cloudflare. In my case, my WAN is a dual stack IPv4 and IPv6, when I call var_dump(dyndnsCheckIP('igb0')) on my WAN; I see that by default the dyndnsCheck(Interface) is returning the IPv6 address on the WAN interface (a public IPv6 in my case).
I happen to have a VLAN defined in my system that only supports IPv4, and when I query that VLAN interface with dyndnsCheck(), I get my public IPv4 address.
So, I updated my Dynamic DNS Client to use the VLAN interface for the "Interface to Monitor" and the IPv4 address on cloudfare updated successfully. Strange workaround, but I'm using it for now. My Cloudflare client settings are as follows:
Service Type: Cloudflare
Interface to monitor: VLAN
Check IP Mode: Automatic (default)
Hostname: @
Domain: xyz.net
Cloudflare Proxy: off
Username: {cloudflare zone id]
Password: [Zone:Edit Token ID]
TTL: empty
Description: CloudflareI have not figured out a way to get "Cloudflare (v6)" client to work and update my AAAA record. If I use the WAN as 'Interface to monitor' which returns an IPv6 address as you would think would be useful, the task fails with the generic error. If I use the VLAN workaround as 'Interface to monitor,' it executes successfully but does nothing on Cloudflare (perhaps fails to overwrite an IPv6 address with an IPv4 address??? don't know).
If anyone can give a clear guide on how to do Dynamic DNS updates to Cloudflare for both IPv4 and IPv6 with a WAN that has the following setup, I would appreciate it :
IPv4 Configuration Type: DHCP
IPv6 Configuration Type: DHCP6 -
Ah, nice catch. Hmm...
-
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
-
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...
