I always just set up root recursors at my home and other locations. I've never noticed any downside.
Choosing a Public DNS Resolver
41–50 of 143 posts
Re: Choosing a Public DNS Resolver
#42unfortunately many DNS resolvers are integrated with CDNs. I do want privacy of an independent non-tracking DNS but I also want my video streaming work fast. :(
Re: Choosing a Public DNS Resolver
#43Does anyone have advice on how to use public wifi alongside DNS resolver? Many public wifi network works need you to use their DNS, so they can redirect you to a gated "accept ToS" screen (and may even require re-approval every 30-60 minutes). To resolve the issue is so frustrating: 1. realize the internet stopped working 2. ping google.com, wait for timeouts to show up. 3. try to guess if its a ISP issue, but then r…
Re: Choosing a Public DNS Resolver
#44Re: Choosing a Public DNS Resolver
#45Does anyone have advice on how to use public wifi alongside DNS resolver? Many public wifi network works need you to use their DNS, so they can redirect you to a gated "accept ToS" screen (and may even require re-approval every 30-60 minutes). To resolve the issue is so frustrating: 1. realize the internet stopped working 2. ping google.com, wait for timeouts to show up. 3. try to guess if its a ISP issue, but then r…
That’s what I’ve been using for years and never had any issues with public hotspots.
Re: Choosing a Public DNS Resolver
#46Does anyone have advice on how to use public wifi alongside DNS resolver? Many public wifi network works need you to use their DNS, so they can redirect you to a gated "accept ToS" screen (and may even require re-approval every 30-60 minutes). To resolve the issue is so frustrating: 1. realize the internet stopped working 2. ping google.com, wait for timeouts to show up. 3. try to guess if its a ISP issue, but then r…
sudo sh -c 'echo "nameserver 192.168.1.1" > /etc/resolver/captive.apple.com'
I did this for an internal website at my university that could only be resolved using the network name server. It just occurred to me that it might also work for the URL macOS uses to detect captive portals. We'll have to see if it works the next time I'm at a café.Re: Choosing a Public DNS Resolver
#47Interesting puzzle on the top level url… what’s that all about ?
Re: Choosing a Public DNS Resolver
#48quad9 seems fine. Glad there are a bunch of alternatives though. We should never stop practicing decentralization in the net.
Be cautious with Quad9; their main address (9.9.9.9) has a "malware" blacklist that has misfired several times already: twice for a private torrent tracker, once for gist.github.com, issue was resolved within minutes to hours. They have a non-filtered address (9.9.9.10), but it doesn't do DNSSEC verification. IMO they're too unreliable to be worth the hassle.
Once Quad9 blocked Halo MCC XBOX Live -> Steam achievements, several fileshare services (probably used for malware somewhere but not my usage) etc...
1.1.1.1 blocked archive.is or got blocked by them or something...
Gone back to Google DNS (gasp) for now, yes as a European... no blocking, fast, never goes down.
Re: Choosing a Public DNS Resolver
#49Earlier quoted context omitted.
I use my own public powerdns dnsdist and recurser/authoritave instances for DoH, DoT, DoQ, TCP and UDP now for ~3 years. Setup took some time, because i used bind, unbound and dnsmasq before. It's super stable and i can also use it on my mobile or legacy devices and as resolver in unbound, adguard/dnsproxy or just in my local resolve.conf.
If its public , how do you prevent others from accessing it?
Re: Choosing a Public DNS Resolver
#50Does anyone have advice on how to use public wifi alongside DNS resolver? Many public wifi network works need you to use their DNS, so they can redirect you to a gated "accept ToS" screen (and may even require re-approval every 30-60 minutes). To resolve the issue is so frustrating: 1. realize the internet stopped working 2. ping google.com, wait for timeouts to show up. 3. try to guess if its a ISP issue, but then r…
On macOS, you might be able to use /etc/resolver to fix this: sudo sh -c 'echo "nameserver 192.168.1.1" > /etc/resolver/captive.apple.com' I did this for an internal website at my university that could only be resolved using the network name server. It just occurred to me that it might also work for the URL macOS uses to detect captive portals. We'll have to see if it works the next time I'm at a café.
echo "nameserver 192.168.1.1" | sudo tee /etc/resolver/captive.apple.com