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

    Dynamic DNS not working

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 5 Posters 11.2k 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.
    • DaReaLDeviLD
      DaReaLDeviL
      last edited by

      Hello,

      I have the following settings -> pfsense -> router all working like expected but not the dynamic dns on a manged account @ dyn.com. I put everthing like in my router. Router does it's job fine (fritbox 7390). But not the dyndns on the pfsense. It detects the change then highlight the old cached ip in red but dont update it again. I have to click edit and save it. Then an update occurs.

      How is it possible that after the cached ip is red an automatic update of the dyn entrie is done?

      I have allready found

      http://redmine.pfsense.org/issues/2166
      http://redmine.pfsense.org/issues/2148

      But this doesnt help me much :-(
      dns1.png
      dns1.png_thumb
      dns2.png
      dns2.png_thumb
      dns3.png
      dns3.png_thumb

      VM PFSense 2.4.3 (amd64) on Dell PowerEdge T410
      Xeon E5620 @ 2.40GHz 2 CPUs: 4GB Ram: 60GB Disk
      ISP (MNet) 1xModem (Vigor 130) 1xWan, 3xLan (PFSense)

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

        You might find something relevant in the dyndns events in the system log.

        1 Reply Last reply Reply Quote 0
        • DaReaLDeviLD
          DaReaLDeviL
          last edited by

          Hmmm not realy?! ???

          Sep 18 21:18:36 php: /services_dyndns_edit.php: phpDynDNS: (Success) IP Address Changed Successfully!
          Sep 18 21:21:19 php: /services_dyndns_edit.php: DynDns: updatedns() starting
          Sep 18 21:21:19 php: /services_dyndns_edit.php: DynDns debug information: 87.139.187.22 extracted from local system.
          Sep 18 21:21:19 php: /services_dyndns_edit.php: DynDns: Current WAN IP: 87.139.187.22 Cached IP: 87.139.187.22
          Sep 18 21:21:19 php: /services_dyndns_edit.php: phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
          Sep 18 21:21:22 php: /services_dyndns_edit.php: DynDns: updatedns() starting
          Sep 18 21:21:23 php: /services_dyndns_edit.php: DynDns debug information: 87.139.187.233 extracted from checkip.dyndns.org
          Sep 18 21:21:23 php: /services_dyndns_edit.php: DynDns: Current WAN IP: 87.139.187.233 Cached IP: 87.139.187.233
          Sep 18 21:21:23 php: /services_dyndns_edit.php: phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
          Sep 18 21:21:27 php: /services_dyndns_edit.php: DynDns: updatedns() starting
          Sep 18 21:21:27 php: /services_dyndns_edit.php: DynDns debug information: 188.174.220.11 extracted from checkip.dyndns.org
          Sep 18 21:21:27 php: /services_dyndns_edit.php: DynDns: Current WAN IP: 188.174.220.11 Cached IP: 188.174.220.11
          Sep 18 21:21:27 php: /services_dyndns_edit.php: phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.

          VM PFSense 2.4.3 (amd64) on Dell PowerEdge T410
          Xeon E5620 @ 2.40GHz 2 CPUs: 4GB Ram: 60GB Disk
          ISP (MNet) 1xModem (Vigor 130) 1xWan, 3xLan (PFSense)

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

            Sorry, I don't really understand your issue.

            Apparently your dynamic DNS entries were updated "recently enough" for them to be not updated at the times of the entries you quoted. If you copied those entries from the web GUI it might be useful to use the pfSense shell command```

            clog /var/log/system.log | grep -i dns

            
            If any of the monitored interfaces has a public IP address an address change will automatically trigger a dynamic dns update.
            
            Your log should contain some lines like the first four lines of
            
            > Sep 19 01:01:03 pfsense2 php: : DynDns: DynDns _update() starting.
            > Sep 19 01:01:03 pfsense2 php: : DNS-O-Matic: DNS update() starting.
            > Sep 19 01:01:03 pfsense2 php: : DynDns: DynDns _checkStatus() starting.
            > Sep 19 01:01:03 pfsense2 php: : DynDns: Current Service: dnsomatic
            > Sep 19 01:01:03 pfsense2 php: : Curl error occurred: Couldn't bind to ''
            
            The next couple of lines may not contain the (case blind) string _DNS_ but give some information about the fate of the update attempt (in the example above, _Curl error occurred: Couldn't bind to ''_ )
            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by

              What does "Curl error occurred: Couldn't bind to" mean?

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                "Couldn't bind to '' " error usually means that it's trying to run on an interface that doesn't actually have an IP address configured on it.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • D
                  deltalord
                  last edited by

                  I have exactly the same issue with No-IP (using ADSL with 24h disconnect). Upon the scheduled disconnect the logfile looks like this

                  
                  Apr 21 02:14:13 pfsense php: : DynDns: updatedns() starting
                  Apr 21 02:14:13 pfsense php: : DynDns debug information: XXX.XXX.31.201 extracted from local system.
                  Apr 21 02:14:13 pfsense php: : DynDns: Current WAN IP: XXX.XXX.31.201 Cached IP: XXX.XXX.25.7 
                  Apr 21 02:14:13 pfsense php: : DynDns debug information: DynDns: cacheIP != wan_ip.  Updating. Cached IP: XXX.XXX.25.7 WAN IP: XXX.XXX.31.201 
                  Apr 21 02:14:13 pfsense php: : DynDns: DynDns _update() starting.
                  Apr 21 02:15:28 pfsense php: : DynDns: DynDns _checkStatus() starting.
                  Apr 21 02:15:28 pfsense php: : DynDns: Current Service: noip
                  
                  

                  but the cached IP within the GUI shows in red and is in fact the old IP given by the ISP. When checking the dashboard I can see that "Current WAN IP" is correct within the logfile, but somehow pfsense doesn't manage to update to the new IP properly.

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