Comment

Comment on [question] Help me access my local homeserver using a public domain name

It does work. In my first edit I’m sharing multiple examples of others making it work, and I’ve made it work in some cases which I explain in my second edit. I’m not using an HTTP challenge, but a DNS challenge which is not specific to any IP address and does not require the IP address to be reachable from outside my network. I only care about accessing the endpoint from within my home network. The use of a real domain allows me to make use of the public chain of trust infrastructure and DNS allowing me to reach my homeserver using any device without having to setup any specific local DNS or installing any custom certificate on any of my devices.

source

Sort:hotnew top

aaravchen@lemmy.zip ⁨7⁩ ⁨hours⁩ ago
Try turning off WiFi on your phone and see if you can connect from there. Connecting from a device within your home network to a another device in your home network is different than connecting from a device out on the internet to a device in your home network. Phone using data is a good way to check that “internet device to home network” case.

source
- TheHobbyist@lemmy.zip ⁨7⁩ ⁨hours⁩ ago
  Works flawlessly with my tailscale setup :) Thanks for asking!
  
  source
non_burglar@lemmy.world ⁨8⁩ ⁨hours⁩ ago
No, it is not fully working.

Many have tried to explain to you that your setup only works for YOU on YOUR subnet.

Your are then asking other public tools meant to lookup public ips with publicly-available DNS names to resolve your internal addresses, which they obviously don’t know anything about, and you’re getting those errors from tools that follow rfc because you are putting the equivalent of “bedroom” on the outside of an envelope and expecting the post office to know that it means YOUR bedroom.

For dns to work properly, the authoritative DNS server should be able to create a reverse lookup record for every a record that allow a DNS client to ask “what record do you have for this IP?” and get a coherent response. Since 192.168.10.0/24 is a non-routable network, you will never have such a reverse record.

Wolfgang has done you a disservice by giving you a shortcut that works as a side-effect of dns before you fully understood how DNS works.

source
- TheHobbyist@lemmy.zip ⁨8⁩ ⁨hours⁩ ago
  
  No, it is not fully working. Many have tried to explain to you that your setup only works for YOU on YOUR subnet.
  
  That’s exactly what I want. I don’t know why you thought I wanted something else? I’m trying to expose reach services in my home network from home, using HTTPS, without requiring a local DNS or to load self-signed certificates.
  
  source
  - non_burglar@lemmy.world ⁨7⁩ ⁨hours⁩ ago
    I know what you’re trying to do, and what those tutorials don’t tell you is that you are shortcutting normal DNS flow, which most apps are expecting.
    
    DNS isn’t designed to work that way, so some apps (like Firefox) with internal hard-coded DNS functions are going to balk at private RFC ips in a DNS record. Or a lack of reverse record.
    
    Again, slow down and think about what your trying to do here. You are complicating your stack for no reason other than you don’t want to set up a local DNS handler.
    
    source
    TheHobbyist@lemmy.zip ⁨7⁩ ⁨hours⁩ ago
    
    so some apps (like Firefox) with internal hard-coded DNS functions Thank you! This was the information I needed! It landed me on this page support.mozilla.org/…/firefox-dns-over-https which shows When DoH is enabled, Firefox by default directs DoH queries to DNS servers that are operated by a trusted partner, which has the ability to see users’ queries and lead me to this page wiki.mozilla.org/Trusted_Recursive_Resolver where I was able to read more about it. That explains why it does not work, I appreciate the insight!
    
    source
    -> View More Comments