Bug #16373
closed
pfSense 25.07 Dynamic DNS Client Failure
0%
Description
Upgrade pfSense to 25.07 and my Dynamic DNS clients now fail with the following error.
```
/services_dyndns_edit.php: Dynamic DNS (host.domain.tld) There was an error trying to determine the public IP for interface - wan (ix2 ).
```
I have multiple clients setup to update Route 53 records and all of them have stopped with the above error.
Please let me know what information I can gather to help troubleshoot this issue. Thanks
Updated by Jim Pingle 28 days ago
- Status changed from New to Incomplete
There isn't enough detail here to identify any specific problem, and this site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum .
See Reporting Issues with pfSense Software for more information.
Updated by Jim Pingle 28 days ago
- Status changed from Incomplete to Not a Bug
This is most likely from the gateway being offline, which is known and not a bug. You can fix the gateway monitoring so it's online and it will work (e.g. change the monitor IP address, let the gw respond to pings, or disable monitoring). There are other forum threads about this, see https://forum.netgate.com/topic/198125/dynamic-dns-ddns-fails-to-obtain-public-ip/43
Updated by Gabriel Zellmer 25 days ago
Jim Pingle wrote in #note-2:
This is most likely from the gateway being offline, which is known and not a bug. You can fix the gateway monitoring so it's online and it will work (e.g. change the monitor IP address, let the gw respond to pings, or disable monitoring). There are other forum threads about this, see https://forum.netgate.com/topic/198125/dynamic-dns-ddns-fails-to-obtain-public-ip/43
Yeah Jim, normally I would spin up a VM and validate it's a bug with a fresh install but I only have one license for Netgate/pfSense 25.07.
I have validated that the Gateway is online, also tried bumping it to offline and back online again and that didn't resolve the issue. Additionally, I booted back into the 24.03 Boot Environment and that immediately did fix the issue.
Is there detailed logs I can pull for the Dynamic DNS client that would help?
Thanks again for the responses!