Fresh install. Expect Pihole to handle all DNS queries.
When I set my EdgeRouter Lite's (gateway 192.168.0.1) DNS to the PiHole (192.168.0.33) I lose internet connection. The PiHole does not appear to be blocking many queries.
https://tricorder.pi-hole.net/kbb8tp8dom
Thanks for any guidance.
This section of your debug log shows quite a bit of activity, from 37 clients:
[2019-09-20 20:20:31.245 7106] Imported 68741 queries from the long-term database
[2019-09-20 20:20:31.246 7106] -> Total DNS queries: 68741
[2019-09-20 20:20:31.246 7106] -> Cached DNS queries: 4524
[2019-09-20 20:20:31.246 7106] -> Forwarded DNS queries: 63758
[2019-09-20 20:20:31.246 7106] -> Exactly blocked DNS queries: 445
[2019-09-20 20:20:31.246 7106] -> Unknown DNS queries: 14
[2019-09-20 20:20:31.246 7106] -> Unique domains: 521
[2019-09-20 20:20:31.247 7106] -> Unique clients: 37
[2019-09-20 20:20:31.247 7106] -> Known forward destinations: 3
Let's see where the activity is coming from and going to:
echo ">top-clients withzero (40)" | nc 127.0.0.1 4711
echo ">top-domains" | nc 127.0.0.1 4711
And from a client that you think should be connected but does not appear to be using Pi-Hole for DNS, run the following:
nslookup pi.hole
echo ">top-clients withzero (40)" | nc 127.0.0.1 4711
0 59907 192.168.0.1
1 2108 127.0.0.1 localhost
2 1427 192.168.0.32 weatherstation.lan
3 952 192.168.0.59 scottserver.lan
4 473 192.168.0.50 scottnas-1.lan
5 452 192.168.0.218 fabriq_bbe8.lan
6 449 192.168.0.163 fabriqchorus_02bc.lan
7 447 192.168.0.215 fabriqchorus_e180.lan
8 445 192.168.0.217 fabriq_33f8.lan
9 444 192.168.0.214 fabriq_5adc.lan
10 440 192.168.0.164 fabriqchorus_ed00.lan
11 249 192.168.0.45 matthews-s8.scottnet
12 204 192.168.0.180
13 190 192.168.0.183 codys-iphone.lan
14 169 192.168.0.49 greys-phone.lan
15 154 192.168.0.53 scottnas-4.lan
16 107 192.168.0.168 greyson-pc.lan
17 86 192.168.0.48 jackson-iphone.lan
18 63 192.168.0.146 masterbedroom.lan
19 61 192.168.0.209 roku4-872.lan
20 47 192.168.0.219
21 37 192.168.0.196
22 28 192.168.0.54 scottnas-5.lan
23 24 192.168.0.230 rbr50.scottnet
24 24 192.168.0.221 500-cc04b40870e7.lan
25 24 192.168.0.223 simons-iphone.lan
26 14 192.168.0.139
27 13 192.168.0.148
28 7 192.168.0.242 mediaroom.lan
29 7 192.168.0.67 familyroomcamera.lan
30 6 192.168.0.225 karins-ipad.lan
31 3 192.168.0.140 localhost.localdomain.lan
32 2 192.168.0.129
33 2 192.168.0.212 hdhr-10720535.lan
34 1 192.168.0.211 rbs50.lan
35 1 192.168.0.42 vzwntwkextdr.lan
36 1 192.168.0.132
---EOM---
echo ">top-domains" | nc 127.0.0.1 4711
0 22132 1.0.168.192.in-addr.arpa
1 10957 196.0.168.192.in-addr.arpa
2 10387 219.0.168.192.in-addr.arpa
3 6913 129.0.168.192.in-addr.arpa
4 6799 148.0.168.192.in-addr.arpa
5 2251 180.0.168.192.in-addr.arpa
6 1422 www.microsoft.com
7 1227 rtupdate.wunderground.com
8 572 avs-alexa-na.amazon.com
9 566 www.yahoo.com
---EOM---
I don't doubt the Pi-hole is being used, but when I lose internet It defeats the purpose.
I think if I can resolve the internet issue I may be good.
If you cannot set the DNS settings on your router for Pi-Hole, how are all the clients connected? Are they using manual DNS settings?
Do you have conditional forwarding enabled to get client names? Without conditional forwarding enabled, are you seeing individual IP's in Pi-Hole?
With conditional forwarding, you have a lot of circular traffic like this shown in your pihole.log:
Sep 20 22:25:12 dnsmasq[14499]: query[PTR] 1.0.168.192.in-addr.arpa from 192.168.0.1
Sep 20 22:25:12 dnsmasq[14499]: forwarded 1.0.168.192.in-addr.arpa to 192.168.0.1
Sep 20 22:25:12 dnsmasq[14499]: query[PTR] 1.0.168.192.in-addr.arpa from 192.168.0.1
Sep 20 22:25:12 dnsmasq[14499]: forwarded 1.0.168.192.in-addr.arpa to 192.168.0.1
Note that all your PTR traffic appears to be from the router, and all for either itself (which is odd) or for clients that don't have names assigned.
I am not being very clear. I can set the router's DNS to use the PiHole. When I do that, the network devices lose internet access. I did have conditional forwarding set on to get client names. I turned that off and it did not make a difference. I do see individual IP address with conditional forwarding turned off.
I had a working PiHole for a long time and somehow the SDCard failed so I literally started from scratch. I never had these issue when I originally set up the PiHole six months ago? If you don't see something obvious it may be best for me to start over ... again from scratch. Maybe I messed something up during the install?
Thanks for your help.
There is one abnormality in your debug log - when the log was run the Pi-Hole was not reachable via it's network interface. There may be a problem with the connection of the Pi to your LAN.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] mkt5857.com is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve mkt5857.com via Pi-hole (192.168.0.33)
[✓] doubleclick.com is 172.217.12.14 via a remote, public DNS server (8.8.8.8)
After you make this change, are you renewing the DHCP lease on the clients? This is the only way to push the new DNS information to them.
One minor item noted in the debug log - you have IP's listed in your whitelist. These do no good. If a device already has an IP, it won't query Pi-Hole for the IP. Devices only query Pi-Hole with a domain name that they want converted to an IP.
-rw-r--r-- 1 root root 7347 Sep 20 20:20 /etc/pihole/whitelist.txt
outlook.office.com
outlook.office365.com
13.107.6.152
13.107.18.10
13.107.128.0
23.103.160.0
40.96.0.0
40.104.0.0
52.96.0.0
131.253.33.215
132.245.0.0
150.171.32.0
191.234.140.0
204.79.197.215
...
Wouldn't be my first choice. I would run pihole -r and select repair first, and see if that improves things. But, from the look of your debug log, the issue is not with Pi-Hole.
Thanks for your help. I will try he repair and remove the IP's from the white list. If that does not improve things .... I'll start over.
I appreciate your time and advice.
Ended up starting over .... all the way back to reformat the SDcard. Everything is working now. I must have messed up the install before.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.