<![CDATA[Dynamic DNS log file noise]]>The Dynamic DNS code (dyndns.class) writes a lot of essentially "debug" type messages to syslog - you will see a lot of them posted here. They clog (pardon the pun) up my syslog because I need to run the dynamic DNS check at regular intervals (some pfSense are not the front-end device with public IP, so they don't see a public WAN IP changing - they need to check regularly what their public IP is). I imagine there are others who would like less output also.
I am happy to clean up the code. I guess the "debug" type messages should be kept in there as an option. Do I add an option on the main Dynamic DNS page for users to enable verbose logging? Or as an option on each Dynamic DNS definition (so some entries could have full logging and others quieter)? Or where is the best place to put a "verbose logging on/off" switch? Or?

]]>https://forum.netgate.com/topic/54370/dynamic-dns-log-file-noiseRSS for NodeSat, 06 Jun 2026 07:32:49 GMTWed, 20 Mar 2013 02:50:52 GMT60<![CDATA[Reply to Dynamic DNS log file noise on Sat, 06 Apr 2013 11:08:40 GMT]]>I made this change a couple of weeks ago: https://github.com/pfsense/pfsense/commit/87b9167234eed690ad6150624169f289f5075625
Now in 2.1 by default it just logs minimal success messages and actual errors. The other "progress scores" that it was logging only come if you enable the verbose logging option in Services->Dynamic DNS, Edit an entry.

]]>https://forum.netgate.com/post/388292https://forum.netgate.com/post/388292Sat, 06 Apr 2013 11:08:40 GMT<![CDATA[Reply to Dynamic DNS log file noise on Sat, 06 Apr 2013 08:53:54 GMT]]>There's a balance between enough logging to know what happened, but not so much that it's unnecessarily spamming the logs. Some of what's there may be better suited to a debug option. Probably an option under System>Advanced, Misc for enabling the debug logging. Just don't silence it entirely or remove so much logging that things pertinent to the majority of use cases aren't there by default.

]]>https://forum.netgate.com/post/388275https://forum.netgate.com/post/388275Sat, 06 Apr 2013 08:53:54 GMT<![CDATA[Reply to Dynamic DNS log file noise on Sat, 06 Apr 2013 08:44:52 GMT]]>@Paul47:

Couldn't you just rig it so a change in the WAN ip triggers a single DNS check, rather than polling?

That is the way it works if the nominated interface has a public IP address. But if the nominated interface has a private IP address then a public web site is polled (by default at about 1am, I think) for the corresponding pubic IP address.

]]>https://forum.netgate.com/post/388274https://forum.netgate.com/post/388274Sat, 06 Apr 2013 08:44:52 GMT<![CDATA[Reply to Dynamic DNS log file noise on Sat, 06 Apr 2013 01:44:44 GMT]]>Couldn't you just rig it so a change in the WAN ip triggers a single DNS check, rather than polling? That way you don't have to worry about the logs getting cluttered.

]]>https://forum.netgate.com/post/388249https://forum.netgate.com/post/388249Sat, 06 Apr 2013 01:44:44 GMT