this post was submitted on 13 Nov 2023
3 points (100.0% liked)

Self-Hosted Main

504 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

One perk that someone told me about is that you can use your domain to get around not having a static IP (because the DNS will compensate).

If I were to get a Cloudflare domain name then what would be some other pros and cons?

you are viewing a single comment's thread
view the rest of the comments
[–] who_you_are@alien.top 1 points 1 year ago (1 children)

tons of subdomains instead of ports

Just to be clear for OP, that applies only for protocols that "support DNS" as in, they send the DNS in the protocol.

The one I have in mind: http(s) and emails.

Games, FTP and most of the protocols don't.

[–] Bagel42@alien.top 1 points 1 year ago (2 children)

Still a bit wrong. You can use things like Portzilla and make it so that certain subdomains are for certain game servers.

[–] cobra89@beehaw.org 1 points 1 year ago

You can also just use a web server like apache and have it forward the traffic to the correct place depending on the sub domain. This is what I do, I can have minecraft.mydomain.com route to 192.168.1.40:5000 and valheim.mydomain.com route to 192.168.1.40:27015.

[–] who_you_are@alien.top 1 points 1 year ago

Hum, then I am missing something because portzilla is just a reverse proxy by the look of it

This mean:

  • you need to use http (games and ftp don't)

Or

  • you have multiple IPs (one per sub domain if I want to go with the examples from portzilla).

I assumed OP was in IPV4 and only has one IP.

Just to be sure from my other assumptions (kinda ELI5)

  • DNS doesn't exist on the transport layer. It is converted to an IP and your computer just try to connect to that IP. So whatever DNS you use, if they point to the same IP you have no way to distinguish from what "DNS" they want to go.

This is how networking works. Only with IP, no DNS.

  • some applications (http), added support for DNS. When the user type a DNS, even if your computer still use IP to reach the server, the browser will introduce itself by telling the server the DNS it tried to reach.