Update 2.7.2 to 2.8.0 Dynamic DNS not working with Cloudflare
-
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.
