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

    How to set destination IP address

    Scheduled Pinned Locked Moved Firewalling
    3 Posts 2 Posters 1.8k 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.
    • A Offline
      amrogers3
      last edited by

      I have a synology storage device. I set up DDNS on it. I had to open up outbound ports 53 and 80 so the DDNS would work correctly.

      So the only web address the synology needs to access is the DDNS web address of "no-ip.com". How can I set up the DDNS outbound destination address in the rules so that the firewall only allows connections to this address over port 80?

      Basically, how to change destination address from "any" to "no-ip.com"?

      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        You could make an alias, and use the no-ip.com hostname in there, but depending on how their site is setup, their hostname may resolve to several IPs and change around at any time, so it may work fine, or sporadically.

        If you really want to filter that, you would need to setup an http proxy (squid) and something (like squidguard) to enforce access by the URL being contacted. Though that could interfere with the dyndns process.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • A Offline
          amrogers3
          last edited by

          @jimp:

          You could make an alias, and use the no-ip.com hostname in there, but depending on how their site is setup, their hostname may resolve to several IPs and change around at any time, so it may work fine, or sporadically.

          If you really want to filter that, you would need to setup an http proxy (squid) and something (like squidguard) to enforce access by the URL being contacted. Though that could interfere with the dyndns process.

          Guess there is not a 100% solution. Thanks for taking the time to answer my question.

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