Devices that have their dns set as the Pihole don't resolve correctly

Help
1

My ISP has provided me with a low-quality router that doesn’t even allow me to change the DNS settings—unless I manually unhide the option in the page’s elements, but even then, any attempt to change it simply fails. To work around this, I set up my Pi-hole as the DHCP server and disabled the router’s DHCP. While most devices successfully connect, some are unable to resolve local DNS, while one device works perfectly. Running an nslookup still returns the router's IP, despite all devices being configured to use the Pi-hole as their DNS server.

Expected Behaviour:

putting a local DNS like Nas.xxx.com should point to 192.168.8.5

Actual Behaviour:

putting a local dns like nas.xxx.abdulksa.com goes to my ISP router

Debug Token:

https://tricorder.pi-hole.net/o2he12Vw/

2

You debug log shows your Pi-hole IP is 192.168.8.4

DNS should be configured as an IP in your devices.
Use 192.168.8.4, not a domain.

3

I am not sure I understand, I have a reverse proxy on another Ip (198.168.8.5) so all traffic should go to reverse proxy to get the certificate but only my PC decided to go through pi hole while all other device seemingly ignore pihole even though their dns is set as the ip of Pi hole (192.168.8.4)

4

good morning, i am not sure how and why but after a nights sleep for some reason all devices decided to start fine now, not sure why

6

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.