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

    No-IP Updating DDNS Address from VPN

    Scheduled Pinned Locked Moved General pfSense Questions
    27 Posts 3 Posters 2.9k 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
      DeathGrin @Bob.Dig
      last edited by

      @bob-dig I am 99% positive I don't have anything else updating Dynamic DNS besides my pfsense box. Here are snippets of the rules you asked for. I also have manual rules in outbound NAT where I was trying to force all traffic destined for anything NOIP for DDNS updates out my main WAN and not vpn.
      Screen Shot 2022-09-30 at 12.34.28 PM.png
      Screen Shot 2022-09-30 at 12.34.51 PM.png
      Screen Shot 2022-09-30 at 12.34.28 PM.png
      Screen Shot 2022-09-30 at 12.37.44 PM.png

      Bob.DigB 2 Replies Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @DeathGrin
        last edited by Bob.Dig

        @deathgrin I don't think you need any of the manual outbound rules (other then xbox) but I am no expert.
        But the rules seem to be ok.

        1 Reply Last reply Reply Quote 0
        • Bob.DigB
          Bob.Dig LAYER 8 @DeathGrin
          last edited by Bob.Dig

          @deathgrin Default Gateway (SystemRoutingGateways) should be WAN, if you haven't checked that.

          D 1 Reply Last reply Reply Quote 0
          • D
            DeathGrin @Bob.Dig
            last edited by

            @bob-dig yeah I have my default WAN manually set to the specific ISP Interface and not set to Automatic.

            Bob.DigB 1 Reply Last reply Reply Quote 0
            • Bob.DigB
              Bob.Dig LAYER 8 @DeathGrin
              last edited by

              @deathgrin Maybe it is a hiding ddclient on some linux server or in your Access-point or something, I don't think it is pfSense.

              1 Reply Last reply Reply Quote 1
              • Bob.DigB
                Bob.Dig LAYER 8
                last edited by Bob.Dig

                Technically we haven't seen the port forwards and 1:1 NAT yet, maybe there...

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  It sure behaves exactly like something updating it from the LAN.

                  The policy based routing rules on the LAN interfaces are never hit by traffic generated on the firewall itself. Even if it's sourced from the LAN interface address. So if changing them affects the ddns client it's almost impossible for it to be the firewall.

                  Yes, those outbound NAT rules are not required except the static ports rule for Xbox.

                  The one with source 'any' will be NATing traffic soured from it's own WAN IP back to it own IP which can break things. It should definitely be removed. Using source 'any' in an OBN rule is almost always a mistake.

                  Steve

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    DeathGrin @stephenw10
                    last edited by

                    @Bob-Dig I don't have any 1:1 rules setup but here are my port forward rules. @stephenw10 I have deleted all of my NAT rules besides for Xbox. I have started a tcpdump to monitor for any traffic going to noip update address for my LAN, so we shall see if anything reaches out.
                    9303c9db-1be7-4ef0-b7b3-e8d4dc6a8ebc-image.png

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      You could also re-enable the ddns rule on LAN and enable logging on it.

                      1 Reply Last reply Reply Quote 0
                      • Bob.DigB
                        Bob.Dig LAYER 8
                        last edited by

                        Or maybe change the credentials for No-IP and only update the pfSense DDNS Client with that, if they use those.

                        D 1 Reply Last reply Reply Quote 2
                        • D
                          DeathGrin @Bob.Dig
                          last edited by

                          @bob-dig @stephenw10 You guys were 100% right... lol. I ended up having it configured through my wireless router (which I had setup as ap mode only). In AP only mode, it hides the ddns configuration... (smh). So when I checked it as a possibility it didn't show up. But after monitoring tcpdump I saw it reach out and try to update, so changed it back to router mode and was able to disable it. Thank you all for your help!

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