4 ms·
I've been using nextdns since I saw it posted on Twitter a few weeks ago. It's been great. I used to run something like PiHole on my home network but ultimatel
by jamesog 7y ago
I've been using nextdns since I saw it posted on Twitter a few weeks ago. It's been great.
I used to run something like PiHole on my home network but ultimately dnsmasq is not a good DNS server so I ditched it. I've been running CoreDNS for a while, forwarding to Google DNS and Cloudflare DNS (both using DNS over TLS) for a while and that worked fine. I'd augmented CoreDNS to serve a hosts file as a blocklist, similar to PiHole.
Nextdns has replaced Google and Cloudflare as forwarders in CoreDNS and it's working really well. I've been liking the proper network-level ad-blocking and being able to use the analytics to figure out what was blocked when something doesn't work.
The nextdns guys are also really responsive and helpful. One of them spent a couple of hours on live-chat with me debugging an analytics issue.
- iuguy 7y agoWhat's wrong with DNSmasq?
- jamesog 7y agoIt's not great as a DNS server. It has some really odd behaviour. One of the things which used to annoy me a lot when using it as a recursor is things like `dig +trace` would just stop at dnsmasq, so you'd have to bypass it by doing something like `dig +trace @8.8.8.8`. Every DNS expert I know says to avoid dnsmasq. It works fine as a DHCP server, though.