Hi,
I wanted to forward the port to my Traefik install on my TrueNAS server. Unfortunately I have now learned that my ISP restricts the range of ports that I can open externally to 12396-12415, so internally I can open port 443 to port 12400 externally. So far so good, but how do I point my Cloudflare DNS record to this port?
My router is a Fritzbox 7530 if that’s relevant.
DNS doesn’t deal with ports, it resolves hostnames to IP addresses and that’s it.
What you probably need is some kind of reverse proxy that sits outside of your network, listens on port 443 and then directs it to your home IP address on port 12400.
The first sentence is not really true though.
If you really want to get anal about it, yes I know there things like CNAME, PTR and MX records too but that’s outside of the scope of this discussion.
DNS doesn’t deal with ports, there’s no way to say:
homelab.example.comshould point to IP address1.2.3.4and port12400.DNS can deal with ports.
You can use a SRV record to specify the port for applications (not browsers) that support it.
For the discussions regarding OPs web server they want externally accessible, no DNS does not do ports.
For other applications there are SRV records, but that’s beyond the scope of the original question. It sounds like u/spacecadet didn’t want to confuse OP, and while SRV can assist certain applications with ports, pointing it out here isnt helpful.
Sure, it’s not helpful, but just because something is out of scope for the original question doesn’t mean you can reiterate objectively false statements.
They probably should have worded it like you did in your first sentence.
That’s just a “well, actually…” response.
Saying it doesn’t do ports is basically just giving the eli5 help the people who are confused usually need. 9/10 the people asking for help are asking about a records or cname records. They want basic DNS help.
When DNS is tought to laymen it’s just translation of a name to an IP, we don’t get into the weeds of rfc xxxx also has DNS provide the configuration of the listening service so the application knows how to communicate. Sometimes it’s best just to lay out the foundation so they can build on that knowledge later.
OP already got “basic dns help” in the top-level responses.
Please build that foundation you mentioned out of correct information.
I only take issue with short and wrong general statements where there is really no need to double down on them.
I have no intent to reply any further.
I agree, people come here to learn. Don’t gatekeep information.
I’d say Nginx Proxy Manager is the easiest reverse proxy I’ve used.
Sure, but the point is not so much about which one to use but that the terminating point listening on 443 should sit outside of his network.
So he will either need a cloud service, or accept that he will have to add
:12400to his URLs.