Selfhosted

39251 readers

267 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Reaching service through domain from local network (lemmy.janiak.cc)

submitted 5 months ago by adidas423@lemmy.janiak.cc to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

I think i have a stupid question but i couldn't find answer to it so far :( When i want to reach a service that i host on my own server at home from the local network at home, is using a public domain effective way to do it or should i always use server's IP when configuring something inside LAN? Is my traffic routed through the internet somehow when using domain even in LAN or does my router know to not do this?

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

[–] TCB13@lemmy.world 6 points 5 months ago* (last edited 5 months ago) (2 children)

is using a public domain effective way to do it or should i always use server’s IP when configuring something inside LAN? Is my traffic routed through the internet somehow when using domain even in LAN or does my router know to not do this?

It depends.

If you control your router (not ISP provided) you can just go into the router settings and tell it to always resolve your public domain to the local machine IP. This will make it so any computer on the network running a DNS query will get a local IP for that domain instead of the public one. Quick and easy fix.

If you don't control it / don't apply the fix above, most likely your traffic is not routed through the internet because routers are usually configured for hairpinning / NAT loopback and they'll simply forward the traffic internally.

You can test what's going on by using the traceroute (or tracert on Windows) to find where the traffic is going. It will give you a line for each host your traffic has to go through in order to reach the destination. If you need help reading the output, just post it public IPs redacted.

[–] adidas423@lemmy.janiak.cc 2 points 5 months ago

Thanks for your reply, i'll try the traceroute thing when i'll be back home in a few days :)

[–] catloaf@lemm.ee 1 points 5 months ago (1 children)

If by "router" you mean the all-in-one box, yes. But even if you don't fully control the device, you can usually change DHCP DNS so that LAN clients will use your local DNS servers.

[–] TCB13@lemmy.world 2 points 5 months ago (1 children)

But even if you don’t fully control the device, you can usually change DHCP DNS so that LAN clients will use your local DNS servers.

Not all ISPs allow this. Mine for instance doesn't allow changing any LAN DHCP setting... fortunately they have an option to configure one of the ports as "bridge" and you'll get a public IP there so I can just plug my own equipment and do whatever I want.

[–] BearOfaTime@lemm.ee 0 points 5 months ago

Not all isps allow this.

Hence the "usually" in their statement.