Facing issues with maintaining device connections to DNS services
Facing issues with maintaining device connections to DNS services
You're facing some tricky connectivity challenges across multiple platforms. It sounds like your devices are generally working well except when using certain configurations. Here are a few points to consider:
- Android appears to be the most reliable for NextDNS connections.
- Proton VPN seems to interfere with tracking, even when enabled.
- iOS works smoothly, which is encouraging.
- Windows is inconsistent; it sometimes fixes itself but often doesn't.
- MacOS and Linux are functioning better than expected, though you're unsure about Linux due to ongoing issues.
- Your TP Link router isn’t supporting NextDNS consistently.
For troubleshooting, you might want to:
1. Verify your VPN settings on each device—ensure it's not blocking NextDNS.
2. Check if the correct DNS server is being used (NextDNS vs Cloudflare).
3. Try disconnecting and reconnecting each device to see if the issue persists.
4. Update firmware or reinstall apps if possible.
5. Consult nextdns.com for device-specific troubleshooting guides.
Let me know if you'd like more detailed steps for any of these!
NextDNS manages DNS resolution by providing a service that translates domain names into IP addresses. You don’t receive a direct IP address; instead, it handles the mapping and updates so your requests reach the correct servers.
Two IP addresses are available. Different installation approaches exist for each device.
For the computers, are you using your DNS server as the router or the NDNS provider? Is a fallback option configured? Also verify on the router. Regarding the phones, there should be an option to manually set up DNS, though this depends on the device. In short, I connect my router to a pihole that points to 1's, so all network traffic goes through it. Then I use a WireGuard VPN to route everything back through my home network for my mobile devices. Latency remains strong even when traveling long distances.
For the computers, as discussed, I use the NextDNS app on Windows, and on MacOS and iOS I rely on the profiles they generate. Here are a few setup examples; visibility depends on logging in. The aim was to avoid configuring each device separately and instead manage it through the router. But since the router isn’t performing well, I’m uncertain about next steps. I think it should behave similarly to PiHole, but hosted elsewhere rather than locally. Perhaps I’ll consider setting up a PiHole later, though current stock problems, high costs, and time constraints make me hesitate. I’m unclear about pointing PiHole to 1’s either. I haven’t adjusted Wireguard settings at all, and it seems Proton VPN doesn’t support WireGuard across all platforms yet.
A Pi 3b is accessible worldwide for its listed price of 35USD, making it more than sufficient for a pihole. The setup process requires roughly 30 minutes, primarily spent on image processing. 1.1.1.1 is Cloudflare's DNS; reach out to their support if issues arise. Otherwise, simply use the IP address it should resolve to wherever needed.
They can watch every DNS query you make… I prefer to run it myself. You don’t have to use a RasPi to set up Pi-hole. I’ve had it on an older system and their Docker configuration makes adding or updating super easy. If not, just assign the router’s DHCP address, so any device gets the right DNS server automatically.
I might take that path. I’ll need a spot in the house for it, since there aren’t many working outlets right now. The base costs about $35, but I’ll likely need a power supply, a protective case, an SD card, and an Ethernet cable—roughly another $100 after shipping. It’s a bit pricey, but if PiHole simplifies things compared to NextDNS, I’d be open to trying it. Unfortunately, NextDNS only offers support through its forum, which is very quiet. That could be a plus since the Raspberry Pi community is so active. Will I get access to blocklists like HaGeZi’s on PiHole? They seem really committed to privacy, so I wasn’t too concerned. I rely on them as much as I trust Proton, Mullvad, and many other privacy services I’ve chosen. I don’t have any old hardware left, or else I’d probably give it another shot! Although I’ve attempted Docker before, it’s always been a challenge for me. I’m really bad at networking stuff, even though I’m okay with a computer. I thought about running PiHole on my Synology, but I wasn’t sure if it’s safe to handle DNS on a NAS and risk messing up the whole network. Plus, I can’t figure out Docker either, so it doesn’t really matter now. I hope I’ll improve in these areas as I keep adjusting and experimenting.
Running Pi-hole on your NAS via Docker is safe and straightforward. This is the method I follow (though my server uses Debian). In the worst scenario, if it fails and you set its IP as DNS, just revert to 1.1.1.1. For setup, install Docker, create a docker-compose.yml file following their guidelines, then execute the pull and start commands to get Pi-hole up and running.