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

    Dynamic DNS not updating on the secondary WAN

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 361 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.
    • M
      mascar
      last edited by

      Dear PFSense experts,

      Please I would like to ask for some help as I can't resolve this issue.
      The Dynamic DNS is not updating with the errors on the logs below.

      background:
      I've been using PFSense for years and I am not sure when the issue started, probably in the last 1 to 4 months.
      I am on pfsense 2.7.0-RELEASE (amd64).
      I have 2x WAN connections online: 2x 1gbps links: WAN01 and WAN02, each one on a different network.
      The Dynamic DNS is from no-ip.
      I have dynamic DNS on WAN01 and WAN02. For WAN01 is working on hostname AAAA , For WAN02 is not working on hostname BBBB.
      If I change the interface for hostname BBBB to WAN01, it works.
      If I change the interface for hostname AAAA to WAN02, it stop working.

      Looks like the problem is related to the interface WAN02.

      I am using the DNS Resolver as DNS solution and both LAN's are there for network interfaces and WAN's are selected there outgoing network interfaces.
      On General Setup, i have 2x DNS servers configured, one on each interface.

      WAN02 is on interface igb2
      I don't have any opt3 interface.

      I already tried to remove and re-add the configuration and also setup and group update, the problem persist.

      with Enable verbose logging checked, it generated the following logs:

      Oct 24 23:49:00 php-fpm 14753 /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
      Oct 24 23:49:00 php-fpm 14753 /services_dyndns_edit.php: Dynamic DNS noip (BBBB): _checkIP() starting.
      Oct 24 23:49:00 php-fpm 14753 /services_dyndns_edit.php: Dynamic DNS noip (BBBB): 223.XX.XX.XXX extracted from local system.
      Oct 24 23:49:00 php-fpm 14753 /services_dyndns_edit.php: Dynamic DNS (BBBB ): running get_failover_interface for opt3. found igb2
      Oct 24 23:49:00 php-fpm 14753 /services_dyndns_edit.php: Dynamic DNS noip (BBBB): _update() starting.
      Oct 24 23:50:15 php-fpm 14753 /services_dyndns_edit.php: Response Header:
      Oct 24 23:50:15 php-fpm 14753 /services_dyndns_edit.php: Response Data:
      Oct 24 23:50:15 php-fpm 14753 /services_dyndns_edit.php: Dynamic DNS noip (BBBB): _checkStatus() starting.
      Oct 24 23:50:15 php-fpm 14753 /services_dyndns_edit.php: Curl error occurred: Failed to connect to dynupdate.no-ip.com port 443 after 75023 ms: Couldn't connect to server

      Any help is appreciated.

      Kind Regards,

      mascar

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @mascar
        last edited by

        @mascar said in Dynamic DNS not updating on the secondary WAN:

        I don't have any opt3 interface.

        This might only be the internal name used in pfSense for that interface.
        You can check this in Status > interfaces.

        Oct 24 23:50:15 php-fpm 14753 /services_dyndns_edit.php: Curl error occurred: Failed to connect to dynupdate.no-ip.com port 443 after 75023 ms: Couldn't connect to server

        Seems pfSense cannot access the update server using the WAN02 gateway.
        Can you access anything using this WAN line?
        Is the WAN2 gateway shown up as 'online'?

        For investigation you can add a policy routing rule to your LAN for the destination 'dynupdate.no-ip.com' (have to create an alias for this) and route it to the WAN2 gateway. Put this rule to the top of the LAN rule set and then try to access the server from a LAN device.

        M 1 Reply Last reply Reply Quote 0
        • M
          mascar @viragomann
          last edited by

          Hi @viragomann,

          Thank you for your reply.

          No opt3 my interface list only igb and vmx interfaces but from the downloaded configuration it looks like opt3 is the reference for the interface - looks like no issues here.

          Both WAN01 and WAN02 Gateways are online and active.
          I tried the policy based routing you mention and it works, I am able to ping the dynupdate.no-ip.com with WAN01 or WAN02 selected as destination (I also confirmed the hits on the rule during both tests).

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