i installed on dietpi adguard+unbound but its seems unbound not resolve dns. i can connect internet without problem.
there is some settting what i did. What i missing ?
(Sorry for that I sent photo separately because form not allow me sent im new user. maybe administrator can join it)
Ok there is some misunderstanding on the configuration.
Did you installed AGH from dietpi-software?
yes installed adgurd and unbound inside dietpi software
Yes this is expected due to unbound config.
What I don’t understand is the setting you have done on your first picture. Actually AGH is asking itself.
And what exactly is your issue or use case. AGH is usually acting as DNS server for network devices. As a best practice DietPi themselves hosting AGH will not use AGH but a global upstream DNS.
I left the first picture blank at first, nothing changed. So no matter what I do, Adguard works alone, Unbound doesn’t work at all. How do I run Adguard and Unbound together?
How i will understand unbound working fine ?
Why do you believe unbound not working?
From which device do you do the DNS leak test? If it’s from the unbound/adguard device then your requests does not go through unbound, but the global DNS (which is a good thing, like Joulinar already said. Imagine unbound fails, then you have also no working DNS on the device itselfs)
Try the test from a device which connects to your router. Of course you need to change the DNS server in the DHCP settings of your router to use your unbound/adguard device.
adguard and unbound working on raspberrypi. i put raspberry static ip adress on my windows dns. i check on windows .
The way is, client > AGH > unbound > root DNS.
Your client will use AGH, always. Unbound is used by AGH only, never used by clients directly
I may have forgotten to mention it but I get internet from another router. My outdoor device distributes the connection it receives from outside to the house with the access point, so the router’s IP address and access point IP addresses are different. The access point’s dhcp is closed, it gets the IP directly from the main device. So the raspberry pi is connected to the access point with an ethernet cable
The device that gives the main device IP address is 192.168.1.1
The access point IP address is 192.168.170
The raspberry pi IP address is 192.168.1.55
When I check Adguard, I see that the main device is using the DNS address, so everything seems fine but unbound is not working
It still seems like you don’t understand how DNS works, especially the connection between AGH and Unbound. The setting you show has nothing at all to do with regular DNS resolution. As you can see on the screenshot, this is a setting for local requests only, such as PTR requests. Typically, the router is entered there. But as I said, this has nothing to do with the normal DNS resolution. The connection to Unbound is set up automatically by dietpi-software during installation and is maintained in AGH in a completely different place. If Unbound is not running, the DNS resolution would not work at all.
Ok but how do I know if unbound is working properly? Isn’t there a test way to do this?
i disabled unbound with sudo systemctl disable unbound
after i tried reach internet . internet working good same. nothing changed
And you are sure your client is connecting to AGH correctly? And on AGH status page you see which upstream DNS?
