Adguard DNS - New Version - Features needed to compete

[coltonshipley]

Hey guys! So I currently use NextDNS, I would gladly convert and use your upcoming setup. However, some things I didn't see if your screenshot.

1. DNS url rewrites. I need to be able to add custom dns entries. like *.local.domain.tld points to 192.168.x.x This helps with VPN stuff as well as home network stuff. Its nice to have it managed in one place.

2. setup instructions/scripts for routers. Example I have a Unifi Dream Machine and NextDNS has a script that installs it on the router itself, and uses dns-over-https (or a similar protocol) You guys would also benefit from something similar.

Both of these things could be part of your plan. I just didn't see it in your blog post screenshots. Any input would be amazing.

Thank you!

[ameshkov]

Most likely for the routers, we will suggest using AdGuard Home with AdGuard DNS configured as an upstream.

[coltonshipley]

Most likely for the routers, we will suggest using AdGuard Home with AdGuard DNS configured as an upstream.

Interesting approach. It would work, no doubt, seems like an odd way to do it.

"Hey run a full dns ad blocker locally and maintain it, but only so you can use our other hosted ad blocker."

[ameshkov]

@neruve heh, well. There will be three options:

1. Your router supports encrypted DNS. Everything is easy in this case.
2. Your router does not support encrypted DNS, but it runs Linux and you have access there. In this case the way is to use either AdGuard Home or dnsproxy.
3. Your router only supports plain DNS. In this case the only option would be to "link" your IP so that AGDNS could understand who's connecting to it.