Gargoyle Forum

Ok, in order to better understand what was going on, I put logqueries to 1 in order to see the DNS queries into the log of the router and ... I discover that once pi-hole (192.168.0.88) is forwarding a request from a computer (192.168.0.10) to DNS server of my ISP, the router seems to catch it and m...

I am lost.. Here the log from the moment I change the DNS server up to the first warning about the number of concurrent DNS request. I am not expert enough..the sole strange thing I see is all this "nameserver" line with IP that I don't know and look weird... Is this normal? using nameserv...

Is there a way to have more detailed log from Gargoyle?

From Pi-Hole forum ( https://discourse.pi-hole.net/t/loop-between-pi-hole-and-router/1105 ): Maybe your router does something silly like DNS catching (100% hypothetical): First with router set to ISP DNS and one of your computers set to Pi-hole DNS computer asks Pi-hole for address Pi-hole asks ISP ...

I do agree that it seems like a loop... needs to understand where and why

If it help, when I changed the DNS in Gargoyle, here is what was going on on the log. Extract: Sun Jan 1 19:14:03 2017 daemon.info dnsmasq[20633]: using nameserver 95.142.171.235#53 for domain micro Sun Jan 1 19:14:03 2017 daemon.info dnsmasq[20633]: using nameserver 95.211.32.162#53 for domain micr...

So in dhcp.conf I changed rebind_protection to 0 and rebooted the gargoyle router...unfortunately it doesn't change anything

Sounds promising, thanks!
How can I allow my local server to resolve dns instead of stopping the full rebind protection?
I don't really understand the rebind-localhost-ok option

So on one computer (connected through lan to the router), I manually set the DNS to 192.168.0.88 and it works flawlessly. Then I tried again to update the gargoyle router DNS field and put back 192.168.0.88 and then all connected equipments were not working anymore (except the one which DNS was manu...

No... will give it a try!