this post was submitted on 05 May 2026
0 points (50.0% liked)
Ubiquiti
756 readers
1 users here now
Unofficial Ubiquiti community.
Discover innovations, troubleshoot, and optimize your Ubiquiti products and software.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
DNS doesn't cover ports. I think Port Address Translation as part of NAT does this? I'm aware of it but never had to use it.
For example you could route traffic using default ports to non default ports. A browser uses 80 and 443 but you could make a rule hitting www.example.com to go to 192.168.0.100:8081 and the browser doesn't know or care.
Or you could use a remote desktop client set to use rdp.example.com:7777 but gets translated to the usual 3389 so you don't have to change any of the RDP servers to listen on different ports.
I haven't touched this in years and I know shitall about reverse proxies so I hope I'm not misleading you but this is where I would start if it were me.