Adguard DNS (Private Beta) vs AdGuard Home Plugin

Started by mush2020, May 08, 2022, 04:40:26 PM

Previous topic - Next topic
I need some help in moving from AdGuard Home installed via Opnsense plugin to new private beta AdGuard DNS
As per the AdGuard DNS beta, requires to add AdGuard DNS servers plain and DoT in devices like router,windows pc,etc..
I have already running AdGuardHome plugin with Unbound works fine.
But want to try the new AdGuard DNS beta
So i need to uncheck AdGuardhome from services to stop the service
I'm not sure what setting to change in Unbound and whether i need to stop unbound services.
In General i think i need to add AdGuard DNS servers 94.140.14.49 ,94.140.14.59, but not sure how to add AdGuard DoT Server tls://device_identifier.d.adguard-dns.com in Opnsense.
Unbound accepts only IPs in DoT settings.

Instead of running and processing DoT from Opnsense i wan to try from AdGuard externally

Any guide or further comments would be appreciated

I did this via unbound.

Go into unbound and under dns over tls. You should have four fields in unbound "DNS over TLS". Domain, Server IP, Server Port, and Verify CN". If you don't what version of OPNSense are you running?
Add each server it gives you. Should be 2 x ipv4 and 2 x ipv6(if you use ipv6)
Put in the IP address in the ip address box and the full hostname in the cn box, and 853 for the port.
This way unbound is handling everything locally and forwarding all requests to Adguard. Issue here unlike nextdns is that adguard will see everything as one device.

Thanks for guide.
Are you still running AdGuardHome Service.
If i disable AGH i dont have internet working.
I'm not sure what to do about NAT rules and Unbound Ports, if AGH is stopped.
Should Unbound listen to its default port, rather then custom due to AGH port in use.