Selfhosted

37780 readers

318 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

Need help with port forwarding and Cloudflare DNS records (lemmy.dbzer0.com)

submitted 10 months ago by [email protected] to c/selfhosted

19 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] brygphilomena 10 points 10 months ago (1 children)

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.

[–] [email protected] -4 points 10 months ago (1 children)

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.

[–] brygphilomena 5 points 10 months ago (1 children)

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.

[–] [email protected] 3 points 10 months ago (1 children)

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.

[–] [email protected] 2 points 10 months ago

I agree, people come here to learn. Don’t gatekeep information.