Comment

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

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

Sort:hotnew top

TheHobbyist@lemmy.zip ⁨3⁩ ⁨weeks⁩ 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
- non_burglar@lemmy.world ⁨3⁩ ⁨weeks⁩ ago
  Glad you figured it out.
  
  source
  - TheHobbyist@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago
    Yes, I now managed to make it fully work on firefox too, needed to set network.trr.allow-rfc1918 to true in the about:config settings! :)
    
    source
- sem@lemmy.blahaj.zone ⁨3⁩ ⁨weeks⁩ ago
  Does DoH stand for DNS over HTTPS in this case?
  
  I’ve run into similar problems as you, and am now in the habit of adding my mydomain.TLD to the exceptions for DNS over HTTPS.
  
  source
  - TheHobbyist@lemmy.zip ⁨2⁩ ⁨weeks⁩ ago
    Yes it does. Are you using Firefox? And you can’t resolve local ip addresses, so that’s why you are setting this exception?
    
    source
    sem@lemmy.blahaj.zone ⁨2⁩ ⁨weeks⁩ ago
    I am not a very good sysadmin. All I remember is the DoH feature was causing me problems in accessing my LAN servers.
    
    I have it a little different than you: I have a halfbaked split-DNS system wherein nc.mydomain.TLD resolves to my public IP address in public DNS, and then on the LAN, the router and the pihole both have DNS entries saying that nc.mydomain.TLD points to 192.168.1.10 . I know I should just have one DNS provider for simplicity or do it better somehow, but I don’t want a single point of failure BC the raspberry pi has failed in the past.
    
    That’s why I started out setting an exception in firefox. I’ve since put other LAN-only services on mydomain.tld, and I think I was having trouble resolving those too without the exception. But unlike you I don’t have private ips in public DNS, although AFAIK that’s a fine practice.
    
    source
    -> View More Comments