DDNS issue after upgrading to 2.8.0

Bubbadoge 0

posted orginally here https://www.reddit.com/r/PFSENSE/comments/1mjm7n8/issue_with_ddns/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
troubleshooting this for days now with no resolution, someone else posted they had the same issue, figured this might be a bug with 2.8.0
"
Got a new pfsense firewall, reinstalled everything, was a update from 2.7.2 > 2.8.0 from my old one
But i did a fresh install and reconfiguration of everything
And while configuring DDNS running into a weird behavior/issue that i didn't encounter before
When i try to force a update this is all it does

/services_dyndns_edit.php: Dynamic DNS: updatedns() starting
/services_dyndns_edit.php: Dynamic DNS (x.domain.com) There was an error trying to determine the public IP for interface - wan (igc2 ).

and thats it, verbose logging shows the same thing
Now it will never be able to determine the public ip as im double NATed behind my ISPs equipment
so my wan connection is 192.168.0.5 gw 192.168.0.1

i have check ip mode set to "Always use the check ip services"
which i then have tried configuring multiple check IP services to see if maybe was some other issue, to no luck, it never tries to use them instead it only checks the GW and thus fails.
"

patient0

@Bubbadoge-0 what DDNS provider are you using? If it's Cloudflare, check

https://forum.netgate.com/topic/198125/dynamic-dns-ddns-fails-to-obtain-public-ip/
https://forum.netgate.com/post/1219168

Reading through the first link is a good starting point.

Bubbadoge 0

@patient0 yep thank you, after reading that back and forth lol
it seems like this was the issue somewhat
https://forum.netgate.com/post/1221290

For some reason, i had 2 WAN GWs, 1 from the install, and 1 that i manually set, this is what it looked like

the second i deleted WAN_DHCP
i went to the DDNS page, and everything started working just fine.

that is definitely some weird behavior, when i have
"always use the check ip services"
i expect it to not have to check anything else but the check ip services. Seems like some bug that its still checking the interfaces for a WAN ip

stephenw10

New behaviour for dyndns in 2.8 is that it will not attempt to check a WAN that has a gateway that's offline. So some configs that were previously working even though there was some issue there will now show the issue such as this.