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

    Dynamic dns multi wan

    Scheduled Pinned Locked Moved Routing and Multi WAN
    11 Posts 2 Posters 876 Views 2 Watching
    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.
    • V Offline
      viragomann @erdeidominik99
      last edited by

      @erdeidominik99
      Add a static route for the update server pointing to the WAN2 gateway.

      1 Reply Last reply Reply Quote 0
      • E Offline
        erdeidominik99
        last edited by

        Okay, but the update server is the pfsense itself.

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

          @erdeidominik99
          pfSense insn't a dynamic DNS server.

          1 Reply Last reply Reply Quote 0
          • E Offline
            erdeidominik99
            last edited by

            Pfsense has that functionality at services.

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

              @erdeidominik99
              You're talking about this
              cf6167fc-0f63-45c7-aee3-15dcb808e13a-grafik.png
              ?

              That is the client config page as you can read. You may add here clients to update dynamic DNS services.
              And for the server used in your client you should add a static route.

              1 Reply Last reply Reply Quote 0
              • E Offline
                erdeidominik99
                last edited by

                Yes, I talked about that, but if I add a static route to pfsense to my dnydns server that won't affect the ip lookup only the interface where the update sent from. So if I do that it will still use my primary wan's ip.

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

                  Doesn't your dynamic DNS service use that IP, where the update request comes from?

                  E 1 Reply Last reply Reply Quote 0
                  • E Offline
                    erdeidominik99 @viragomann
                    last edited by

                    @viragomann Yes, but the pfsense caches the primary wan's ip, so it wont't send update when the second wan's ip changes.

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

                      @erdeidominik99
                      Even when you select the second WAN at "Interface to monitor" in the dynDNS client settings?

                      1 Reply Last reply Reply Quote 0
                      • E Offline
                        erdeidominik99
                        last edited by

                        Yes, I selected the second wan at the send from and at the interface to monitor, added a static route, and the cached ip is the first wans ip, but the ddns has the right ip, because the request was sent from the second wan. So it works, but it won't update when the ip changes, because te pfsense monitors the primary wan.

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