Ubiquiti local DNS

Networking & Firewalls
1

I just watched the excellent Lawrence video on setting up local DNS on Ubiquiti, and decided to try it on my proxmox node. The node is X11.myname.net at 10.10.60.21. Proxmox GUI is on port 8006. Not sure what I’m missing, but the GUI will not connect with X11.myname.net. but will connect with when :8006 is appended to the FQDN . What’s the fix for this? This will also be a problem with Docker, since all the containers are on the same IP with different ports. Thanks

2

Hostnames on their own have no way to convey port information, they only map a name to (one or more) IP addresses. Applications will use the port implied by the protocol if you don’t specify one - 80 for HTTP, 443 for HTTPS, etc.

Some specific applications have support for additional DNS records, like Minecraft supports “SRV” records to provide the port number for a specific server, but web browsers don’t support his (I’m not aware of any), and Ubiquiti hasn’t put support for them in their interface either.

1 Like
3

So, what you are saying is that it won’t work on Ubiquiti, and I would have to use Pihole or something similar?

4

No, you still need to put the port number after the hostname, the same as you did with the IP address.

5

If you are looking for something that can handle both the port number and creating a certificate then you would want a reverse proxy such as NGINX Proxy Manager.

2 Likes
6

No, what @brwainer is saying that this isn’t really a DNS problem. This is a port problem. If you want to reach your hostname without the port then you have 2 options.

  1. A reverse proxy to proxy the IP and port to a standard 443 port and get the added benefit of SSL
  2. Change your proxmox port to use 443.

Edit: Tom beat me to it.

1 Like
7

thanks, that is what I’ll do. Need to watch that video!

8

Looks like option one is going to be best for me, I checked out option 2 and it looks like it would be easy (at least for me) to screw something up

1 Like
9

Then there would be option number three: not worrying about the port number attached to the URL. After all, you don’t have to type it in every time, as modern browsers have great features such as bookmarks and autocomplete. :wink:

There may be other reasons to put a reverse proxy in front of it, such as obtaining valid certificates, but Proxmox can also issue those directly, so that alone wouldn’t convince me to use a reverse proxy either. Also, if you use SPICE for remote desktop and have a reverse proxy on port 443 in front of it, you might run into issues, because the DNS for X11.myname.ne then points to the IP of your Reverse Proxy but SPICE is listening on Port 3128 on the Proxmox host. In that case, you would have to tinker with that to make it work.

In any case, the port number alone wouldn’t be a reason enough for me to deal with a reverse proxy, but maybe that’s just me. :wink: