4 ms·
I have some unusual, from the normal browser user perspective, DNS stuff and this just leads to a bunch of questions. My gateway has a bunch of static DNS entr
by Mister_Snuggles 7y ago
I have some unusual, from the normal browser user perspective, DNS stuff and this just leads to a bunch of questions.
My gateway has a bunch of static DNS entries for internal hosts, which are all in a fake top-level domain. How will resolving these work if the request goes to CloudFlare? CloudFlare obviously doesn't know about my internal domain. Currently my gateway resolves what it knows about and uses my ISP's DNS to resolve what it doesn't.
Pi-Hole is presents a similar problem.
Finally, if DoH is the future, how do I run my own DoH server which can resolve internal hosts? Does such software even exist yet? How do I point Firefox at this DoH server? The relevant Wikipedia article[0] points to a list of public DoH servers I can use, but offers no insight as to what software I'd use to run one for my own use.
[0] https://en.wikipedia.org/wiki/DNS_over_HTTPS https://en.wikipedia.org/wiki/DNS_over_HTTPS
- qmarchi 7y agoYour setup will still work. Firefox is configured with a "fallback" situation, where anything that doesn't resolve on the public resolver will be queried again using your system-configured DNS options. As for Pi-hole, my recommendation is to block NATed traffic to Cloudflare's DoH traffic (forcing it into Fallback mode) and then setting up Pi-Hole to use for it's recursive resolution. Alternatively, you can setup your own DoH server based off BIND: https://terminaladdict.com/networking/linux/2019/09/13/DoH.html https://terminaladdict.com/networking/linux/2019/09/13/DoH.h...
- ignoramous 7y agocloudflared, knot-resolver, stubby, unbound, CoreDNS can be run as DoH and/or DoT stub and/or recursive resolvers, locally. The easiest stub resolver to setup would be nextdns' client: https://github.com/nextdns/nextdns https://github.com/nextdns/nextdns