Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dynamic DNS log file noise

    Scheduled Pinned Locked Moved DHCP and DNS
    5 Posts 4 Posters 5.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      phil.davis
      last edited by

      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?

      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

      1 Reply Last reply Reply Quote 0
      • P
        Paul47
        last edited by

        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.

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          @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.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • P
              phil.davis
              last edited by

              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.

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.