I created a fresh install on a brand new rp4 and a asus rt ax68u. I'm using the firebog list for the block list. I used the pihole5 list tool to grab the lsit for me. I've set the Lan dns ip to the pihole and set the pihole to a static ip.
I have know idea where to start I order to trouble shoot this.
Asus arrt ax68u running merlin. Raspberry pi 4 2gb
Everything is a fresh install.
Edit: I just want to thank everyone for all the help they are providing.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Do you have two Pi-holes then (one on the Pi4 and one on the Asus)? How are you using two?
In their Adlists section you should see at least one adlist present, and on the Dashboard it will show how many domains are on the adlists and whether any queries are coming in and are blocked. The Query Log will show anything that has come in, you can refresh it for updates. How does all that look when you check it out?
Your router is probably handling DHCP for your network, ie you join your wifi and you're online. Go into your router and find the DHCP section and you should see DNS settings in there. It will have its own address in there, ie telling devices to use the router itself for DNS. You need to change that to be the address of your Pi-hole so it tells devices to use your Pi-hole instead. Then save the changes. Finally, come off your network for a moment and then back on to pick up the new settings. This all depends on the router and what it allows, but that's the general idea to start using Pi-hole automatically.
I only have one pihole running. It's on the rp4 2gb. The asus router was a completely fresh install on factory settings of merlin. I should have made that more clear. I just wanted to convey that I had not changed anything other then the Lan dns. The weired thing is the pi was getting qureis just wasn't blocking anything.
The pi had a static ip address and the router was set to use the pi as the dns.
Thank you for all the help so far.
Thank you for that info. I tried this and it would always fail to upload the log. I have the log file but unsure if I can upload it here or if I have to upload it else where.
This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.
sudo nano /etc/resolv.conf
Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit
Run
pihole -d
and upload the debug log.
Thank you for that info. It was successful in uploading the file.
From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of these commands:
nslookup pi.hole
nslookup flurry.com
nslookup flurry.com 192.168.50.205
Here you go. Once again thank you for the help.
C:\Users>nslookup pi.hole
Server: dns.google
Address: 8.8.8.8
*** dns.google can't find pi.hole: Non-existent domain
C:\Users>nslookup flurry.com
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: flurry.com
Addresses: 34.225.127.72
74.6.136.150
98.136.103.23
212.82.100.150
54.161.105.65
C:\Users>nslookup flurry.com 192.168.50.205
Server: pi.hole
Address: 192.168.50.205
Name: flurry.com
Addresses: ::
0.0.0.0
On the last command we forced the use of Pi-hole as DNS server and the answer was 0.0.0.0, as expected.
But the other 2 tests showed Pi-hole is not used by your Windows machine.
It is using Google DNS (8.8.8.8). That's why it's not blocking.
Did you set this DNS manually on your Windows machine?
No the windows machine is pulling it from the router. The router is set ti use the pihole and the upstream fro the pihole is the Google dns. (8.8.8.8).
I should mention the pihole is blocking some ads on my pixel phone bit not all of them. Right now it's just the Google sponsored search results.
No, the nslookup command you ran from that client tells you explicitly that it has been told to use 8.8.8.8 as the DNS resolver; if the client had been configured to use your router as the DNS resolver, the router address would have appeared in the "Address: ...." line in your response.
So either you have manually set the client to use 8.8.8.8 as the DNS server, or the DHCP information your client is getting from the DHCP Server is telling it to use 8.8.8.8.
If the DHCP server is your router, then it needs to be altered under the LAN settings to reflect your Pihole address. This is under the Advanced Settings (Merlin) and LAN settings (DNS Server 1 and DNS Server 2). You can set "Advertise router's IP in addition to user-specified DNS" to No.
This is different from the router's WAN DNS; under Merlin Advanced/WAN, you can specify a public DNS like 8.8.8.8 or just let it use the ISP-provided (Automatic) DNS. If you tell the WAN settings to use Pihole, you have to make sure Pihole's Conditional Forwarding is not enabled or set to use the router.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.