The Mac is still using the router as the nameserver, and does not appear to have accepted the changes you made in your settings.
Sorry, there was a gap in time and my setting was off. I re-ran the code with my DNS set to the pi and I got the expected outcome,
nameserver 192.168.1.11
The thing is, when I have my DNS server set to the pi(192.168.1.11) I lose internet access
With the namserver on the Mac set to Pi-hole, you are unable to resolve DNS queries? With the nameserver set to 192.168.1.11, what is the output of the following from the Mac?
nslookup pi.hole
$ nslookup pi.hole
;; connection timed out; no servers could be reached
I ran pihole status on the pi:
pi@raspberrypi:~ $ pihole status
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
I previously had this running on a pi at 192.168.1.20 (simple install, worked effortlessly)
Could there be leftover configuration settings somewhere that are forcing something to the wrong ip?
Please send us a new debug token with your current configuration.
All the indications are that there is a connectivity problem between the Pi and the router. In this section of the debug log, Pi-hole is checking to see if it can resolve a known blocked domain using the outward facing IP of the Pi, and it is failing. I don't think this is a Pi-hole issue, it's a network issue. Neither the Pi-hole nor the Mac can access the Pi-hole at that IP, and the indications are that that IP isn't processing the traffic.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] pksbialapodlaska.pl is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve pksbialapodlaska.pl via Pi-hole (192.168.1.11)
[✓] doubleclick.com is 172.217.7.14 via a remote, public DNS server (8.8.8.8)
OK, I'm not surprised because recently I my wifi cut out randomly (etho still worked), and after some troubleshooting I did a full reset on my router. Afterwards WiFi came back, but pi-hole stopped.
Any suggestions on next steps would be appreciated!!
Nothing more than logical network troubleshooting. Eliminate things one at a time until you find the solution. Power supply, hardware problem, bad cables, etc.
The pi is able to connect to the internet though, and works locally to share files.
The hardware is the same as it was when pihole worked the first time... Thanks for trying
I got it to work.
Netgear Nighthawk R6700v3 AC 1750
Router runs DHCP
Router set primary and secondary DNS servers to pi-hole
Reserved IP on router
eth0 connection
Cloudflare as upstream DNS server
Not sure what solved it, but the last thing I did was disable the WiFi on the pi (sudo ifconfig wlan0 down) (if you need to switch it back: sudo rfkill unblock wifi). I went into pi-hole admin > settings > DNS > "Listen only on interface eth0". Maybe just a coincidence, but it works either way.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.