Pihole not forwarding after resolving DNS

Help
1

I previously had Pihole running really well on Jessie until it one day just stopped resolving queries. Since then I've tried reinstalling it, updating to Wheezy and reinstalling but still have the same issue. It should, after resolving the host direct me to the website but it seems to stall at this point. All I get is "looking up [website]" in the browser. For a while it would resolve Google but no other sites.

I tried setting it to use wlan0 instead of eth0 as someone else said it worked for them but it didn't change anything for me.

pihole -t gives the following output:

01:06:41 dnsmasq[8884]: reply www.google.com is 2404:6800:4006:808::2004
01:06:41 dnsmasq[8884]: query[PTR] 100.203.58.216.in-addr.arpa from 127.0.0.1
01:06:41 dnsmasq[8884]: forwarded 100.203.58.216.in-addr.arpa to 122.56.237.1
01:06:41 dnsmasq[8884]: reply 216.58.203.100 is syd09s15-in-f4.1e100.net
01:09:34 dnsmasq[8884]: query[A] snippets.cdn.mozilla.net from 192.168.1.1
01:09:34 dnsmasq[8884]: forwarded snippets.cdn.mozilla.net to 210.55.111.1
01:09:34 dnsmasq[8884]: forwarded snippets.cdn.mozilla.net to 122.56.237.1
01:09:36 dnsmasq[8884]: query[A] snippets.cdn.mozilla.net from 192.168.1.1
01:09:36 dnsmasq[8884]: forwarded snippets.cdn.mozilla.net to 210.55.111.1
01:09:36 dnsmasq[8884]: forwarded snippets.cdn.mozilla.net to 122.56.237.1
01:13:11 dnsmasq[8884]: query[A] signal.auto.mydlink.com from 192.168.1.1
01:13:11 dnsmasq[8884]: forwarded signal.auto.mydlink.com to 210.55.111.1
01:13:11 dnsmasq[8884]: forwarded signal.auto.mydlink.com to 122.56.237.1
01:13:11 dnsmasq[8884]: query[A] files.dlink.com.au from 192.168.1.1
01:13:11 dnsmasq[8884]: forwarded files.dlink.com.au to 210.55.111.1
01:13:11 dnsmasq[8884]: forwarded files.dlink.com.au to 122.56.237.1

So in my limited knowledge it seems to be doing some resolving. The web interface says that there have been 131 queries and 4 have been blocked so it's clearly doing something, just not the whole process.

pihole -d gives the following debug token of uxko5zcf02

2

Wheezy is not an update of Jessie :smiley:

What website do you mean ?

You can run Pi-hole connected through WiFi without any problems.

On Windows and Linux clients, you can run below command to query the OS configured DNS server(s) for diagnosing:

nslookup pi.hole

Or lookup a naughty domain:

nslookup doubleclick.com

Or if want to query a particular DNS server like for example Google's 8.8.8.8:

nslookup doubleclick.com 8.8.8.8

Below results on a client of mine with 10.0.0.2 being my Pi-hole setup:

$ nslookup pi.hole
Server:    10.0.0.2
Address 1: 10.0.0.2 noads.dehakkelaar.nl

Name:      pi.hole
Address 1: 10.0.0.2 noads.dehakkelaar.nl

$ nslookup doubleclick.com
Server:    10.0.0.2
Address 1: 10.0.0.2 noads.dehakkelaar.nl

Name:      doubleclick.com
Address 1: 10.0.0.2 noads.dehakkelaar.nl

$ nslookup doubleclick.com 8.8.8.8
Server:    8.8.8.8
Address 1: 8.8.8.8 google-public-dns-a.google.com

Name:      doubleclick.com
Address 1: 172.217.20.78 ams15s33-in-f14.1e100.net
3

Restart FTL and Dnsmasq and see if that fixes anything (the logs showed they were having some trouble):

sudo service dnsmasq restart
sudo service pihole-FTL restart
4

Thanks for your reply.

I meant to say Stretch, not Wheezy. Apologies for that.

When I say [website] I mean any website I try to visit, which is why it's in the square brackets.

I know you can run Pihole through ethernet or wifi, it was that I looked at someone else's issue that was resolved and it worked through wifi but not ethernet but I didn't get the same result.

Still having the same issue sadly.

5

I've tried restarting the services and no luck. I've now installed Stretch Lite and tried it again but still getting the same problem. The log shows that it has forwarded the request but there's no response.

I've run pihole -d again and my new token is a4zhgulzhd. It seems odd that it worked completely fine for quite a while and then started having issues which don't seem to be fixed with reinstallation. Could there be something wrong with the pi itself?

6

What happens if you try these commands on the Pi-hole?

dig google.com
dig google.com @8.8.8.8
dig pi.hole
dig pi.hole @8.8.8.8
7

I tried installing Pihole on a different pi and it worked perfectly so there must be something wrong with the original one. It's all working great now.

1 Like