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

    DynDNS fails to update multiple hostnames on same account

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    5 Posts 3 Posters 2.0k 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.
    • G
      Gandi
      last edited by

      First off I'm not sure if this is 2.0-specific bug!

      I have 2 DynDNS hostnames I want to keep updated, both of them on the same account.
      The problem I'm having is that only one of them is being updated, the other isn't touched by pfSense. (although it does display the correct cached IP for both hostnames in Services->Dynamic DNS, only one of them really has my current WAN IP cached)
      Both entries have the exact same configuration apart from the hostname (DynDNS dynamic, no MX, no wildcards, no description)

      I'm currently running on 2.0-BETA4 (i386)
      built on Thu Nov 11 00:34:31 EST 2010
      but I've noticed the problem alot earlier already :(

      1 Reply Last reply Reply Quote 0
      • J
        jlepthien
        last edited by

        Logs…

        | apple fanboy | music lover | network and security specialist | in love with cisco systems |

        1 Reply Last reply Reply Quote 0
        • G
          Gandi
          last edited by

          My apologies! :D
          Seems like it's trying to update the same hostname twice, unless I'm misinterpreting the logs of course.

          Dec 4 17:42:22 check_reload_status: reloading filter
          Dec 4 17:42:21 php: : Resyncing openvpn instances configurations for interface WAN.
          Dec 4 17:42:17 php: : Sending HUP signal to 56474
          Dec 4 17:42:15 php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
          Dec 4 17:42:15 php: : DynDns: Cached IP: 88.66.199.99
          Dec 4 17:42:15 php: : DynDns: Current WAN IP: 88.66.199.99
          Dec 4 17:42:14 php: : DynDns debug information: 88.66.199.99 extracted from local system.
          Dec 4 17:42:14 php: : DynDns: _checkIP() starting.
          Dec 4 17:42:14 php: : DynDns: _detectChange() starting.
          Dec 4 17:42:14 php: : DynDns: updatedns() starting
          Dec 4 17:42:14 php: : DynDns: Running updatedns()
          Dec 4 17:42:12 php: : phpDynDNS: (Success) IP Address Changed Successfully! (88.66.199.99)
          Dec 4 17:42:12 php: : phpDynDNS: updating cache file /conf/dyndns_wandyndns.cache: 88.66.199.99
          Dec 4 17:42:12 php: : DynDns debug information: 88.66.199.99 extracted from local system.
          Dec 4 17:42:12 php: : DynDns: _checkIP() starting.
          Dec 4 17:42:12 php: : DynDns: Current Service: dyndns
          Dec 4 17:42:12 php: : DynDns: DynDns _checkStatus() starting.
          Dec 4 17:42:12 php: : DynDns: DynDns _update() starting.
          Dec 4 17:42:12 php: : DynDns debug information: DynDns: cacheIP != wan_ip. Updating. Cached IP: 88.66.199.55 WAN IP: 88.66.199.99
          Dec 4 17:42:12 php: : DynDns: Cached IP: 88.66.199.55
          Dec 4 17:42:12 php: : DynDns: Current WAN IP: 88.66.199.99
          Dec 4 17:42:12 php: : DynDns debug information: 88.66.199.99 extracted from local system.
          Dec 4 17:42:12 php: : DynDns: _checkIP() starting.
          Dec 4 17:42:12 php: : DynDns: _detectChange() starting.
          Dec 4 17:42:11 apinger: Starting Alarm Pinger, apinger(5657)
          Dec 4 17:42:11 php: : DynDns: updatedns() starting
          Dec 4 17:42:11 php: : DynDns: Running updatedns()
          Dec 4 17:42:11 dnsmasq[41434]: using nameserver 8.8.4.4#53
          Dec 4 17:42:11 dnsmasq[41434]: using nameserver 8.8.8.8#53
          Dec 4 17:42:11 dnsmasq[41434]: using nameserver 4.2.2.2#53
          Dec 4 17:42:11 dnsmasq[41434]: reading /etc/resolv.conf
          Dec 4 17:42:09 check_reload_status: reloading filter
          Dec 4 17:42:09 apinger: Exiting on signal 15.
          Dec 4 17:42:09 dnsmasq[41434]: no servers found in /etc/resolv.conf, will retry
          Dec 4 17:42:09 dnsmasq[41434]: no servers found in /etc/resolv.conf, will retry
          Dec 4 17:42:06 apinger: ALARM: GW_WAN(88.66.199.1) *** down ***

          1 Reply Last reply Reply Quote 0
          • E
            Efonnes
            last edited by

            I think this is something that is already supposed to be fixed.  Update before reporting an issue next time.

            1 Reply Last reply Reply Quote 0
            • G
              Gandi
              last edited by

              Yeah sorry, I tried searching for the issue but couldn't find any recent topics, hence the skip of update.
              Anyhow it really seems to be resolved with the newer snapshots, so thanks!  :)

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