this post was submitted on 28 Jun 2026
23 points (96.0% liked)

Selfhosted

60210 readers
832 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I have some subdomains that go to my home address (I know I should put it through a VPS first but I'll get to that when I have time).

If I connect to example.domain.tld and DNS records point back to my own IP, where does that data go to reach back to my device?

Edit: thanks for the responses everyone

you are viewing a single comment's thread
view the rest of the comments
[–] NarrativeBear@lemmy.world 1 points 9 hours ago

What you are looking for is something called NAT Reflection/HairPin NAT/NAT loopback.

When you search for a "domain.example.com" your router loops you back at your reverse proxy and all the traffic remains "internal". Your website will still be externally accessible (the ones you setup to be).

Here's a example of how to set this up on PfSense router.

https://www.youtube.com/watch?v=ngwae1UvS-Q