Facing issues with maintaining device connections to DNS services
Facing issues with maintaining device connections to DNS services
We recently relocated. It’s unclear what the prior tenant did to mess with the wiring, but they certainly made some unusual choices. I plan to install a Raspberry Pi and test it out. I’ll maintain NextDNS usage, since I need it to function independently of my network without relying on Tailscale or similar services.
Ignore the VPN details. If you go through that route, all traffic—especially to websites or domains—will pass through it. Each computer should automatically pick up the next DNS entry, but only if your network uses either IPv6 or IPv4 exclusively. Not both. It’s possible you have both IPv4 and IPv6 DNS addresses in your router, which is why I usually suggest turning off IPv6 on all systems and routers. This is unnecessary for a local area network, and since your public IP from the provider is IPv4, IPv6 doesn’t add much value unless you need to reach devices outside your local network. I’m not sure IPv6 is essential even then. Block more sites and check the next DNS log or the analytics section. It’s likely the analytics link. For Android, switching to a different DNS/firewall app made things clearer—I used the https option instead, which felt simpler. I can also use it with cellular, but I don’t need it because my current app already supports device-level domain blocking. I suspect you’re overriding your DNS settings for IPv6, and turning it off might help. Also, I have Pi-hole set up in a VirtualBox Debian system, which is straightforward thanks to the virtual bridged adapter—no confusing Docker or YAML files needed.