and the tail of the pihole log should have looked something like this:
Jul 18 15:22:22 dnsmasq[9251]: query[A] www.cnx-software.com from 192.168.0.135
Jul 18 15:22:22 dnsmasq[9251]: forwarded www.cnx-software.com to 127.0.0.1
Jul 18 15:22:22 dnsmasq[9251]: reply www.cnx-software.com is 104.28.19.95
Jul 18 15:22:22 dnsmasq[9251]: reply www.cnx-software.com is 104.28.18.95
Jul 18 15:22:22 dnsmasq[9251]: query[A] cdn.rawgit.com from 192.168.0.135
Jul 18 15:22:22 dnsmasq[9251]: forwarded cdn.rawgit.com to 127.0.0.1
Jul 18 15:22:22 dnsmasq[9251]: query[A] dsh7ky7308k4b.cloudfront.net from 192.168.0.135
Jul 18 15:22:22 dnsmasq[9251]: gravity dsh7ky7308k4b.cloudfront.net is 0.0.0.0
Jul 18 15:22:22 dnsmasq[9251]: query[A] www.googletagservices.com from 192.168.0.135
Jul 18 15:22:22 dnsmasq[9251]: gravity www.googletagservices.com is 0.0.0.0
Jul 18 15:22:22 dnsmasq[9251]: query[A] pagead2.googlesyndication.com from 192.168.0.135
Jul 18 15:22:22 dnsmasq[9251]: gravity pagead2.googlesyndication.com is 0.0.0.0
Jul 18 15:22:23 dnsmasq[9251]: query[A] s.skimresources.com from 192.168.0.135
Jul 18 15:22:23 dnsmasq[9251]: gravity s.skimresources.com is 0.0.0.0
Jul 18 15:22:23 dnsmasq[9251]: query[A] s.w.org from 192.168.0.135
Jul 18 15:22:23 dnsmasq[9251]: forwarded s.w.org to 127.0.0.1
Jul 18 15:22:23 dnsmasq[9251]: reply cdn.rawgit.com is <CNAME>
Jul 18 15:22:23 dnsmasq[9251]: reply rawgit.rawgh.netdna-cdn.com is 151.139.237.11
Jul 18 15:22:23 dnsmasq[9251]: reply s.w.org is 192.0.77.48
Jul 18 15:22:23 dnsmasq[9251]: query[A] www.google-analytics.com from 192.168.0.135
Jul 18 15:22:23 dnsmasq[9251]: gravity www.google-analytics.com is 0.0.0.0
Jul 18 15:22:23 dnsmasq[9251]: query[A] s7.addthis.com from 192.168.0.135
Jul 18 15:22:23 dnsmasq[9251]: gravity s7.addthis.com is 0.0.0.0
Jul 18 15:22:23 dnsmasq[9251]: query[A] steadfastsystem.com from 192.168.0.135
Jul 18 15:22:23 dnsmasq[9251]: gravity steadfastsystem.com is 0.0.0.0
Jul 18 15:22:23 dnsmasq[9251]: query[A] z-na.amazon-adsystem.com from 192.168.0.135
Jul 18 15:22:23 dnsmasq[9251]: gravity z-na.amazon-adsystem.com is 0.0.0.0
Jul 18 15:22:23 dnsmasq[9251]: query[A] quantcast.mgr.consensu.org from 192.168.0.135
Jul 18 15:22:23 dnsmasq[9251]: gravity quantcast.mgr.consensu.org is 0.0.0.0
Your pihole log shows none of the requests for the domains on that website - the only requests shown in your log are from the Pi itself (127.0.0.1). The DNS traffic from that client did not go through Pi-Hole.
Yes I do have a PC with Windows. I have set my router as other provider to turn off the DHCP from my provider. After that I enabled the DHCP server on Raspberry pi hole and chose the cloud DNS as upload DNS server.
I don't know what am I doing wrong. It's really frustrating. Should I post the screen shots of my pi hole DNS settings here for correction?
Hi, can you pls post the DNS server settings on pihole for me pls. I don't know what I am doing wrong only some ads are getting blocked not all.
Here is the screenshot of my settings.
Correct me what u am doing wrong. Thanks
It's 01:15 in the midnight. I am really very tired from work and typing from bed. Can I give you the output of this tomorrow? May be in 7 hrs from now?
Thanks
On the PC, manually map the DNS to the IPv4 address of the Pi, and disable IPv6. This will eliminate IPv6 and the router as potential sources of the problem.
I didn't get you. What exactly do you want me to do? If I disable ipv6 on pc will it disable on pihole ?
What are the DNS settings I should choose in pihole?
Change the DNS settings on the PC to manually point to Pi-Hole. If you do not know how to do it, then do a web search and you will find many videos and instructions.
No.
Don't change anything in Pi-Hole. As noted in two previous replies, this is not a Pi-Hole configuration problem.
One thing worth mentioning for future reference, I had devices looking for IPv6 DNS which, oddly enough, on my ISP provided router has a different set of DNS config pages. That was annoying.. I noticed it on iOS devices which tend to prefer IPv6 in a big way.
You have to tell the devices to use Pi-hole. It can not intercept and replace.
I think you need to spend some time reading https://docs.pi-hole.net and see how it works, how to install it and how to configure your clients and network to use Pi-hole. Until you understand the basics of how things work then any troubleshooting we do will be of little use.