Mesh routers for NextDNS?
I like all the benefits listed for using the NextDNS app: https://help.nextdns.io/t/m1hmv0k/which-setup-type-to-use
Are there any Mesh routers that I can install NextDNS on so I can get these benefits?
- Easy to setup
- Traffic is encrypted and server is authenticated
- Does not require IP linking
- Advanced routing / fallback mechanism
- Network wide device identification when installed on the router
I've done the whole custom firmware on WRT54G in another life and just want something easy with no maintenance now. I've had the Google Wifi system for a few years but that doesn't allow the NextDNS app to be installed on it (yes, I'm using the NextDNS DNS entries but I want the full experience).
-
You can have it on a rpi on the side and point your LAN DNS on it.
-
Olivier Poitrey My LAN DNS has 2 entries to fill out. Would I have both of them set to the Raspberry Pi? How much maintenance is requires for the Rpi?
-
Killua Zoldyck yes, point them both to the RPI. Make sure it's the LAN DNS and not the WAN DNS. There is no maintenance, it's a very simple small DNS proxy, statically linked single binary.
-
Olivier Poitrey So instead of a RPi, I'm using my MacMini. I installed the CLI and had it listen on port 53, report-client-info, auto-activate, config 123456, setup-router
I then updated my router (Google Wifi) and set it to use the IP of the MacMini for DNS.
Things are functional. But for most of the traffic in Logs (on the NextDNS site), I see the Device name as: e1f064...0e27c
I think that Device is the Google Wifi router.
Is there any way to have the Logs show the actual Device name instead of the Google Wifi Router? (Without having to install apps on every client)
-
Killua Zoldyck you can try to add the option dns-discovery pointing to the IP of your router.
-
Olivier Poitrey It seemed like it gave me some other names for devices but the names didn't make sense. And then it caused problems with my router.
There has to be an easier way to Identify devices without having to configure each device individually.
-
Olivier Poitrey
the google WiFi router requires unique IPs for primary and secondary. I put one of the NextDNS IP as secondary. That way if the Pi device fails, there is a second DNS (albeit unencrypted) to the NextDNS.
-
