this post was submitted on 31 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

515 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
communick@selfhosted.forum
1
Personal domain or not? (alien.top)
submitted 1 year ago by Sajberspejs@alien.top to c/main@selfhosted.forum
8 comments fedilink hide all child comments
 

I have a personal domain name. I got it because my first name was available with my country tld.

I use it for email, which I will most likely keep forever, but how about my self-hosted stuff?

I use Slack's Nebula to access my self-hosted resources externally.

Would you mind exposing your VPS:es IP:s to the world by adding them as subdomains? In my case lighthouse1.myname.tld and lighthouse2.myname.tld?

I feel much more secure using DuckDNS for those IP:s as it should make it much harder to identify my attack surface.

Does it make sense or am I just paranoid?

I really don't like the idea of my attack surface being easily identifiable just by my email or first name.

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

My approach is using Nginx and wildcard subdomains. The specific subdomain name that accesses the service is not listed in DNS anywhere and just knowing the IP address doesn't get you anything since m.y.i.p:443 is just getting you an nginx landing page.

[โ€“] Verum14@alien.top 1 points 1 year ago

ngl the wildcard sub idea is a good one