All ads showing on all sights despite setting up pi-hole exactly how I have done in the past, been through the FAQs and cant seem to figure out why
Ads not being blocked
https://tricorder.pi-hole.net/1omDtSpB/
Thank you so much if anyone has time to help
Your debug log shows that Pi-hole is working properly and that domains are being blocked.
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
nslookup pi.hole
nslookup flurry.com
nslookup flurry.com 192.168.1.109
Hi thanks for responding, I may have jumped the gun, some add do seem to be getting blocked now, but Id interested to know if there are still some issues from the output
(base) Brendans-MacBook-Pro:~ b$ nslookup pi.hole
Server: 151.236.14.64
Address: 151.236.14.64#53
** server can't find pi.hole: NXDOMAIN
(base) Brendans-MacBook-Pro:~ b$ nslookup flurry.com
Server: 151.236.14.64
Address: 151.236.14.64#53
Non-authoritative answer:
Name: flurry.com
Address: 127.0.0.1
(base) Brendans-MacBook-Pro:~ b$ nslookup flurry.com 192.168.1.109
Server: 192.168.1.109
Address: 192.168.1.109#53
Name: flurry.com
Address: 0.0.0.0
(base) Brendans-MacBook-Pro:~ b$
There are multiple DNS servers answering.
One blocking (192.168.1.109) and the other (151.236.14.64) not.
On the Mac run:
scutil --dns
Have a read below:
This client is not using Pi-hole for DNS. It is using the DNS server at IP 151.236.14.64.
The second command provides an interesting result. Flurry.com was not resolved to the correct IP, but rather was resolved to the loopback IP, which is typical if the domain is contained in a hosts file.
Non-authoritative answer:
Name: flurry.com
Address: 127.0.0.1
The third command forces the DNS query to go to Pi-hole, and Pi-hole correctly answers.
Your problem is not with Pi-hole, it is likely in that client. Your DHCP server is passing out two local IP's for DNS, both of which are this Pi-hole:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 548 bytes from eth0:192.168.1.1
Offered IP address: 192.168.1.106
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 86400 ( 1d )
netmask: 255.255.255.0
router: 192.168.1.1
dns-server: 192.168.1.109
dns-server: 192.168.1.109
--- end of options ---
DHCP packets received on interface lo: 0
DHCP packets received on interface eth0: 1
Your problem does not appear to lie with Pi-hole. Fix the DNS on the MacBook Pro and see if that resolves your problem.
151.236.14.64 I saw here as well when Surfshark was active. Shouldn't be active but it was. Disconnected from Surfshark and everything was working properly. Noticed this as I noticed no new entries in the querylog from my laptop Which was odd.
So I guess Brendans Macbook Pro is running a VPN, f.e. Surfshark.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.