Bug #12753
closedDynDNS entries not being updated in one netgate box
0%
Description
Hello everyone,
I've two netgate boxs in HA with 22.05.2, both with multi WAN (but at the time only ix0 NIC have an internet connection above), with the same setup on Dynamic DNS, all with dyndns.org entries (in this case is just one).
In primary box, all enabled entries seems to be working, on secundary box is not (check attachments with screenshots of webgui).
On webgui logs, the only thing that I have related with warnings or errors about Dynamic DNS or even dyndns.org,is also present on primary box, that is working fine.
Logs on primary box (with verbose mode activated on the entry that is enabled):
Feb 3 11:22:29 php 49616 rc.dyndns.update: Curl error occurred: Failed to connect to members.dyndns.org port 443 after 75011 ms: Operation timed out
Feb 3 11:22:29 php 49616 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): _checkStatus() starting.
Feb 3 11:22:29 php 49616 rc.dyndns.update: Response Data:
Feb 3 11:22:29 php 49616 rc.dyndns.update: Response Header:
Feb 3 11:21:14 php 49616 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): _update() starting.
Feb 3 11:21:14 php 49616 rc.dyndns.update: DynDns (x.getmyip.com): Dynamic Dns: More than 25 days. Updating. 1643887274 - 1640182459 > 2160000
Feb 3 11:21:14 php 49616 rc.dyndns.update: Dynamic Dns (x.getmyip.com): Current WAN IP: x.28.208.226 Cached IP: x.28.208.226
Feb 3 11:21:14 php 49616 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): x.28.208.226 extracted from Check IP Service
Feb 3 11:21:14 php 49616 rc.dyndns.update: Dynamic DNS (x.getmyip.com): running get_failover_interface for opt3. found ix0
Feb 3 11:21:14 php 49616 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): x.28.208.226 extracted from Check IP Service
Feb 3 11:20:02 php 49616 rc.dyndns.update: Dynamic DNS: updatedns() starting
logs on secundary box (with verbose mode activated on the entry that is enabled):
Dec 23 17:40:26 php 98159 rc.dyndns.update: Curl error occurred: Failed to connect to members.dyndns.org port 443 after 15729 ms: No route to host
Dec 23 17:40:26 php 98159 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): _checkStatus() starting.
Dec 23 17:40:26 php 98159 rc.dyndns.update: Response Data:
Dec 23 17:40:26 php 98159 rc.dyndns.update: Response Header:
Dec 23 17:40:10 php 98159 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): _update() starting.
Dec 23 17:40:10 php 98159 rc.dyndns.update: DynDns (x.getmyip.com): Dynamic Dns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: x.x.x.226
Dec 23 17:40:10 php 98159 rc.dyndns.update: Dynamic Dns (x.getmyip.com): Current WAN IP: x.28.208.226 Cached IP: 0.0.0.0
Dec 23 17:40:10 php 98159 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): x.28.208.226 extracted from Check IP Service
Dec 23 17:40:09 php 98159 rc.dyndns.update: Dynamic DNS (x.getmyip.com): running get_failover_interface for opt3. found lagg0.4090
Dec 23 17:40:09 php 98159 rc.dyndns.update: Dynamic DNS dyndns-custom (x.getmyip.com): x.28.208.226 extracted from Check IP Service
Dec 23 17:40:03 php 98159 rc.dyndns.update: Dynamic DNS: updatedns() starting
From each box, I am able to reach that SSL url:
Running: /usr/local/bin/nmap -sS -e lagg0.4088 'members.dyndns.com'
Starting Nmap 7.91 ( https://nmap.org ) at 2021-12-23 16:50 WET
Nmap scan report for members.dyndns.com (162.88.175.12)
Host is up (0.17s latency).
rDNS record for 162.88.175.12: vip.web1-05-ussnn1.prod.dc.dyndns.com
Not shown: 998 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 13.04 seconds
Curling that 443 port, on members.dyndns.com from everywhere, I got a 404 error.
Curling to 80 port on checkip.dyndns.org, it works as expected.
Dynamic DNS was working before on secundary box, but I've made several updates in both systems, and have only noticed this, several weeks ago.
What I have done:
- Copy that entry
- Recreated that entry
- Reboot this secundary box
I've check two other netgate boxs still in 2.4.5-release-p1, with entries that use dyndns.org, with the same login of those netgates in HA, and I dont have those:
Dec 23 17:40:26 php 98159 rc.dyndns.update: Curl error occurred: Failed to connect to members.dyndns.org port 443 after 15729 ms: No route to host
Now, I am unable to determinate if this failed connection is having impact on that secundary box, not updating that entry.
I think that DynDNS may have changed something that was recently added on latest version(s) of pfsense OS.
If you need more info or data, fill free to ask, and I will provide.
Full track of this issue:
Files
Updated by Jim Pingle about 3 years ago
- Status changed from New to Rejected
- Target version deleted (
22.05)
There isn't enough here to say it's a bug and not a configuration problem, even considering what's on the forum thread.
If there is a bug, it's likely already solved as it might be the same issue as #12631 but until you are running the new release it's difficult to say. Try it again once the new version is out.
If it's still not working as you expect on the new release, then post additional information about your setup on the forum thread, specifically including your outbound NAT rules, interface and VIP configuration, gateway and gateway group configuration (including what the default gw settings are), contents of the routing table during normal operation and during failover, and the DNS configuration (both under general setup and in the resolver or forwarder).