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

    DynDNS not properly updating with 2.1.5

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 667 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.
    • D
      doejohn
      last edited by

      Hello,

      The DynDNS update mechanism for freedns.afraid.org don't seem to work for me.

      When the IP on the PPPoE interface changes, the IP on the "Dynamic DNS" page turns into red (indicating that it is not up-to-date) but the update won't happen.

      The log shows this:

      Jan 9 00:12:18  php: rc.newwanip: DynDns: updatedns() starting
      Jan 9 00:12:18  php: rc.newwanip: DynDns (my.do.main): 1.2.3.4 extracted from local system.
      Jan 9 00:12:18  php: rc.newwanip: DynDns (my.do.main): 1.2.3.4 extracted from local system.
      Jan 9 00:12:18  php: rc.newwanip: DynDns (my.do.main): Current WAN IP: 1.2.3.4 Cached IP: 4.3.2.1
      Jan 9 00:12:18  php: rc.newwanip: DynDns (my.do.main): DynDns: cacheIP != wan_ip. Updating. Cached IP: 4.3.2.1 WAN IP: 1.2.3.4
      Jan 9 00:12:18  php: rc.newwanip: DynDNS (my.do.main): DynDns _update() starting.
      Jan 9 00:12:54  php: /services_dyndns.php: The command '/sbin/route change -inet default dynamic' returned exit code '68', the output was 'route: bad address: dynamic'

      So the update procedure has started.

      When I edit the DynDNS-Entry and klick onto the "Save and force Update" button, the DynDNS-Entry is updated immediately. So the configuration must be correct.

      I guess that the update procedure happens too fast, so that the routing is not set up properly. Maybe the last line of the log is an indication of this? Where does this error come from?

      Why is the update not retried when it is detected that it is not up to date?

      Is there any way to delay the update for a couple of seconds to make sure the routing is set up properly when the update happens? Or maybe to force an update periodically?

      Any ideas?

      PS: this is pfsense-2.1.5

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