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

    Port 53 on 2+ machines

    Scheduled Pinned Locked Moved NAT
    6 Posts 3 Posters 467 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.
    • J
      jason001
      last edited by

      Good day..

      Is there a way to use port 53 DNS on two machines? example virtual server1 and virtual server2? if so.. how do you setup the config for it to be able to work?

      Regards,
      Jason

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by KOM

        You can have a service listening on any port you choose as long as something else isn't already bound to that port. That said, why would you insist on using the well-known DNS port for that? What are you really trying to do, host a game server on a locked-down WAN or something?

        Perhaps if you describe the end result of what you want, we can recommend a better way to get there.

        1 Reply Last reply Reply Quote 0
        • J
          jason001
          last edited by

          @KOM said in Port 53 on 2+ machines:

          lly trying to do, host a game server on a locked-down WAN or something?
          Perhaps if you describe the end result of what you want, we can recommend a better way to get there.

          Two machines. Both different servers.. one is for web other is for DDNS both require port 53 otherwise i would have changed it. im using 1 static IP. but i need to be able to use port 53 on both only reason is because of DNS port 53. i can't install one over the other then the system crash. so i have two separate machines.

          is there a way to config something like that? at the moment port 53 is used for web server. but i need to find another way to make server 2 work..?

          1 Reply Last reply Reply Quote 0
          • KOMK
            KOM
            last edited by

            I still can't get my head around exactly what you're trying to do. If you are trying to access two different servers via tcp/53 then you will need another public IP address to forward the traffic from.

            1 Reply Last reply Reply Quote 0
            • RicoR
              Rico LAYER 8 Rebel Alliance
              last edited by

              Port 53 is not default for Web.
              So if you can manually move it to 53 you can move it to anything other you want, 54, 55, 5353 and so on.
              No need to bind all your services to port 53, especially when you don't use protocol default ports anyway.

              -Rico

              J 1 Reply Last reply Reply Quote 0
              • J
                jason001 @Rico
                last edited by

                @Rico
                port 53 is required for DNS on a CONTROL PANEL! for host.

                also
                the second server machine is hosting DDNS that also require DNS with default port "53"

                What im asking: IS there a way to route port "53 DNS" to pfsense and then from pfsense to machine 1/2 ?

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