I can ping sites using the IP Address but the DNS name won't resolve. I am running a modem from my local provider which the Pi-hole is attached to. The Pi-hole DOES resolve DNS queries just fine. My modem is connected to an Apple Airport Time Capsule. The Time Capsule provides both a 5GHz and 2.4GHz wireless network and its router mode is set to "Bridge Mode". The main router normally provides DHCP addresses although I've changed this so the Pi-hole provides it. I've switched back to my main router providing both DHCP and DNS (which is set to "Automatic" on my router).
Your debug log shows that Pi-Hole is properly resolving DNS queries, as you noted. So, the problem lies elsewhere.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] safety.microsoft.com.wraasqbnl.e8fsosq5cikdcqi.science is 0.0.0.0 via localhost (127.0.0.1)
[✓] safety.microsoft.com.wraasqbnl.e8fsosq5cikdcqi.science is 0.0.0.0 via Pi-hole (192.168.0.225)
[✓] doubleclick.com is 172.217.9.46 via a remote, public DNS server (8.8.8.8)
In the debug log you uploaded, it shows that DHCP is enabled on the Pi-Hole with a lease of 168 hours (7 days). If you have changed this to another DHCP server, all your clients will need to get a new lease for the new settings to be in effect.
You appear to have three devices on your network that can provide DHCP services (modem/router, Apple router, Pi-Hole). Ensure you are only using one of these at a time.
If your ISP-supplied router does not let you change DNS settings, use the Pi-Hole DHCP. Get all the clients new leases and see if that resolves this.
One last item, not related to this issue. You are using Norton ConnectSafe DNS as one of the upstreams in Pi-Hole, and on Nov 15, 2018 this will be discontinued. So make a note to remove this prior to that date.
I had attempted to set things up so that the Pi-hole was serving up DHCP addresses while acting as the DNS server. On my Apple I disabled DNS. On my main router I pointed the DNS server to the Pi-Hole (at least I think I have, the setup is different from what I’ve seen in videos).
I set the Pi-hole to 7 days as that is what the main router was set to.
What I haven’t done is force new leases. How do I go about doing that?
If you have the Pi-Hole serving DHCP, the clients will get their DNS settings from the Pi-Hole. On some routers, there are DNS settings scattered all about, which makes it hard to chase them all down. DNS rebinding, dynamic DNS, IPV6, etc. Can be tedious to find them all. Some people put their ISP modem/router in bridge mode and use a second router to do the routing. You will likely have to try some different options if this doesn't clear up.
This varies by client. You generally want to renew the lease and flush the DNS cache at the same time.
On an IOS device, put in airplane mode for a few seconds, then back out. On a Mac, run this terminal command: sudo killall -HUP mDNSResponder
On a PC, ipconfig/flushdns, then ipconfig/release and ipconfig/renew.
Android, I don't know.
Personal opinion - that's a long time. Any changes don't get to your clients for a week. I generally use 24 hours.
Thanks for your help. Working now, don’t know why . I slept on it, tried a couple of things, didn’t work, slept on it more, came upstairs (where the networking equipment and main computer are), plugged in the Pi-hole and configured my Mac Pro to use the Pi-hole and it worked / resolved with no issue! Then, changed the DNS on my primary server to be the Pi-Hole and that worked with my main computer which is Ethernet attached to the primary router. Tried an old iPad in wireless mode and it is working.
I can see that my Pi-hole is blocking lots of stuff. DHCP is still being handled by my primary modem / router and that seems to be working fine. Still a few more devices to verify but for some reason all seems fine now!
Again, thanks for your help. Oh, I removed reference to Norton as a DNS site. And changed the DHCP expiry to 2 days.
. I slept on it, tried a couple of things, didn’t work, slept on it more, came upstairs (where the networking equipment and main computer are), plugged in the Pi-hole and configured my Mac Pro to use the Pi-hole and it worked / resolved with no issue! Then, changed the DNS on my primary server to be the Pi-Hole and that worked with my main computer which is Ethernet attached to the primary router. Tried an old iPad in wireless mode and it is working.