Unnecessary Dynamic DNS updates
-
So now that things have settled down since 2.2 is released and I'm not updating my pfSense box all the time with new snapshots, I've gone digging for other things on my bone-stock no-packages installation. Looking at the system logs, I have a page full of…
Jan 26 09:17:46 check_reload_status: updating dyndns WAN_DHCP Jan 26 09:17:46 check_reload_status: Restarting ipsec tunnels Jan 26 09:17:46 check_reload_status: Restarting OpenVPN tunnels/interfaces Jan 26 09:17:46 check_reload_status: Reloading filter Jan 26 09:17:47 php-fpm[26002]: /rc.dyndns.update: phpDynDNS (abc.domain.com): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.Over and over again, sometimes as often as a few seconds between blocks, but more often 30 minutes or more. I have over 50 lines of this today, from the time above to the time I'm making this post. There doesn't appear to be any reason that it's doing this, at least that I can tell.
Any thoughts or other things I can look at to try and find the cause?
And no, it's not DHCP on the WAN causing these… lease time is like 4 days or so.
-
what happens right before that "updating dyndns" log? Anything in the system log? If not, the gateways log have anything?
It's not actually updating, since the IP hasn't changed and not enough time has past, so it won't get you banned with your provider as sending excessive updates may do. But that does seem excessive if you have a 4 day lease length.
-
The block I pasted is what is repeated numerous times in the General system log, no other events before each occurrence.
In the Gateways log, the events seem to coincide with delay or loss events from apinger. IMHO, delay events shouldn't cause the other things to happen. Loss events, maybe in some situations, but even that's a stretch to me. I'd rather just have the DDNS updates run on the daily CRON job, DHCP events, and interface events.
Any way I can keep that script from running on those apinger events?
-
It does not update anything. It's just noise. The real issue here is the darned apinger thing being totally overzealous with its default settings (plus buggy to put it mildly).
-
I know it's just noise and that updates aren't actually happening, but it's annoying to see log files filling up with unnecessary stuff like this.
-
Frankly, I don't see what's your trouble with the DynDNS stuff. This is much more annoying
Jan 26 09:17:46 check_reload_status: Restarting ipsec tunnels Jan 26 09:17:46 check_reload_status: Restarting OpenVPN tunnels/interfacesNot only that it's totally and completely useless when nothing changes, worse it
- disrupts traffic
- triggers the darned /etc/rc.newwanip{,v6} scripts that cause a whole lot more of useless activity
- causes a lot of CPU activity on slower boxes
To get somewhere, go to System - Routing - Gateways, edit the WAN GW, click Advanced and make latency/packet loss/internal/down/etc settings a whole LOT more relaxed (defaults noted there).
