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

Self-Hosted Main

502 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
what happens to lan traffic when you leave the local network - home (alien.top)
submitted 10 months ago by Lazy-Fig-5417@alien.top to c/main@selfhosted.forum
7 comments fedilink hide all child comments
 

I have FQDN.

# 1

I did configure unbound on opnsense router to override all hosts of mydomain.com to local IP of my server.

Local server is ruuning SWAG who creates ssl with lets encrypt using dns validation. I did not forward / open any ports on router so those services are NOT accessible from internet.

I can access all my services localy over some_subdomain.mydomain.com

# 2

I did configure DNS records at my registrant to point to my webhosting (normal external company) and create simple html page. So when I am browsing mydomain.com and I am not at home I get that simple page.

question:

I leave home so I am not at home network and not using VPN then my laptop or phone are trying to resolve mydomain.com because some application wants to connect to service. They get IP of webhosting and trying to communicate with it.

Should I be worried about sensitive data being leaked? At least, webhosing can log requestes where it can see my subdomains and url path ...

โ€‹

what is your setup? what is your opinion? is there any better solution beside VPN { I dont want to open VPN always when leaving home }

thanks

you are viewing a single comment's thread
view the rest of the comments
[โ€“] thekrautboy@alien.top 2 points 10 months ago

I use a subdomain for all my local services.

example.com then local.example.com and for the services service.local.example.com

This way i can still use Lets Encrypt but i also have a clear separation between actual services that are public facing and things i keep local only.

Fitting this to your setup when *.local.example.com points as CNAME to your local reverse proxy, then you can access it fine when at home. When youre away and your laptop tries to access it again, it still retrieves a local IP from the DNS, which of course fails, and because of that your webhoster at example.com doesnt receive any attempts at subdomains etc, you completely bypass it.