Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
[ I've configured the pi-hole local DNS to resolve 2 domains.
The first one is called "server.home" and it should resolve to 10.13.2.2 - which is the IP address of the raspberry pi running pi-hole in docker container (on portainer).
The second domain is "hriya.local" which should resolve to my router's ip address 1o.13.2.1:
-os: Linux raspberrypi 6.6.47+rpt-rpi-v7 #1 SMP Raspbian 1:6.6.47-1+rpt1 (2024-09-02) armv7l GNU/Linux
-hardware: raspberry pi 3b]
Actual Behaviour:
[When I use the dig command on these domains, it works as expected returning the right ip address. But when I use the curl or browser for any of these domains - I get "could not resolve domain" error]
Debug Token:
[https://tricorder.pi-hole.net/ql4LtuNy/]
That would confirm that Pi-hole is correctly supplying resolution.
If some software fails to resolve those same local DNS records, that would suggest that it wouldn't be using Pi-hole for DNS, so respective DNS requests would not register with Pi-hole.
For *.local domains, that may be expected, as .local is the TLD reserved for reserved for mDNS protocol usage and should not be used with plain DNS.
You should rename hriya.local to hriya.home, as your debug log shows home is your local/search domain.
And client OSs or browsers may employ DoT or DoH, which would by-pass Pi-hole.
You'd have to verify that those options are disabled.
Hi Bucking_Horn - thanks for the prompt response 
My router is Huawei HG659b and has a setting where you can give the name to the device.
I believe the hriya.home is working because of the the setting on the router.
DNS server settings are
where 10.13.2.2 is the raspberry pi ip where pi-hole is running
I will do a little bit more digging in to disabling DoT and DoH - then post the results here soon
Your router is distributing itself as DNS server, allowing clients to by-pass Pi-hole.
You should remove that secondary DNS server.
Pi-hole has to be the sole DNS server for your network.
EDIT: Make sure your clients renew their DHCP leases in order to receive the updated DNS server information, e.g. by dis- and reconnecting them to your wifi, or by power-cycling them.
Updated the router settings and now Pi-hole is the sole DNS server
Hi again Bucking_Horn, I followed your suggestion to check if DoT and DoH is causing the issue. I disabled the Secure DNS in chrome (flag below)
Once disabled - DNS started working as expected.
Then I enabled the secure DNS setting again. After enabling secure DNS - the domain kept on resolving as I would expect i.e. server.home started resolving fine to the Pi-hole's lighttpd
I am thinking that the chrome probably has cached this entry and it will break again at some stage. Then I will have to again toggle ON/OFF the secure DNS and hopefully it will resolve.
I will consider this resolved for now, do I need to do anything specific to this post ?
Thanks for the prompt reply and all your help.
