No internet for devices connect to Pi-Hole's DNS

Help Community Help
1

The issue I am facing:
My AtomicPi was unplugged and after re-plugging it in, I have not been able to reconnect to the internet with pi-hole's DNS. I also cannot access the web interface when modifying my Mac's DNS to Pi-Hole's IP either.

Details about my system:
I am using an Atomic Pi, the micro sd card may have popped out but it is back in and restarted properly anyways. Running Ubuntu 18.04.4 LTS on it and everything is up-to-date as well.

What I have changed since installing Pi-hole:
I tried changing the resolv.conf's nameserver to 127.0.0.1 which did nothing, then changed it back to 9.9.9.9 or 8.8.8.8. The pi itself has internet access.

I also re-installed pi-hole completely but still no internet for my devices.

Debug Token:
https://tricorder.pi-hole.net/m61u1irabv

2

Do you have DNSSEC enabled? If so, is the time/date on the Atomic correct?

3

I'm not sure if I have DNSSEC enabled though...
It has the correct time/date when using the terminal with "date".

4

Your debug log appears normal, but it doesn't show if Pi-hole is receiving queries from network clients.

What is the output of this command from the Pi terminal - this will show activity for the previus 24 hours, and may not be a true indicator if the Pi was disconnected within that time period:

echo ">stats >quit" | nc localhost 4711

From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

5

It appears normal because I unplugged it, then realized it was no longer allowing the connected devices to have internet. I ended up uninstalling it, then reinstalling pi-hole again removing previous logs...

I'll place that into the original post so it's clearer.

--

For echo ">stats >quit" | nc localhost 4711, I got:

domains_being_blocked 84818
dns_queries_today 131
ads_blocked_today 6
ads_percentage_today 4.580153
unique_domains 21
queries_forwarded 35
queries_cached 66
clients_ever_seen 2
unique_clients 2
dns_queries_all_types 131
reply_NODATA 0
reply_NXDOMAIN 0
reply_CNAME 0
reply_IP 0
privacy_level 0
status enabled

As for the nslookup for pi.hole the return from my terminal on my mac when connected to the Pi-Hole's DNS is the following:
;; connection timed out; no servers could be reached

6

What DNS servers is the Mac using? From the Mac terminal:

scutil --dns

What is the output of this from the Mac terminal:

nslookup pi.hole 192.168.1.209

7

Whenever I test Pi-Hole's DNS I automatically change the server to 192.168.1.209 on the Mac's Network Preferences directly so I am not disrupting other users on my home network.

From my Mac terminal for scutil --dns:

resolver #1
  nameserver[0] : 192.168.1.209
  flags    : Request A records
  reach    : 0x00020002 (Reachable,Directly Reachable Address)

resolver #2
  domain   : local
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300000

resolver #3
  domain   : 254.169.in-addr.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300200

resolver #4
  domain   : 8.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300400

resolver #5
  domain   : 9.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300600

resolver #6
  domain   : a.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 300800

resolver #7
  domain   : b.e.f.ip6.arpa
  options  : mdns
  timeout  : 5
  flags    : Request A records
  reach    : 0x00000000 (Not Reachable)
  order    : 301000

DNS configuration (for scoped queries)

resolver #1
  nameserver[0] : 192.168.1.209
  if_index : 5 (en0)
  flags    : Scoped, Request A records
  reach    : 0x00020002 (Reachable,Directly Reachable Address)

The output of nslookup pi.hole 192.168.1.209:

;; connection timed out; no servers could be reached
8

I assume the Mac has a valid IP on the 192.168.1 range.

Let's take a look at the Pi end. From the Pi terminal:

ip addr

sudo grep -v '#\|^$' /etc/dhcpcd.conf

9

Yes the mac definitely has a valid IP within that range.

ip addr return on pi terminal:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:07:32:4c:ea:34 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.209/24 brd 192.168.1.255 scope global enp1s0
       valid_lft forever preferred_lft forever
    inet6 fe80::9547:97bf:b129:abb1/64 scope link 
       valid_lft forever preferred_lft forever
3: wlx0007324cea33: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 00:07:32:4c:ea:33 brd ff:ff:ff:ff:ff:ff

sudo grep -v '#|^$' /etc/dhcpcd.conf return on pi terminal:

hostname
duid
persistent
option rapid_commit
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option ntp_servers
option interface_mtu
require dhcp_server_identifier
slaac private
interface enp1s0
        static ip_address=192.168.1.209/24
        static routers=192.168.1.1
        static domain_name_servers=8.8.8.8 8.8.4.4
11

There are no UFW or iptables running on that Pi or your network that would interfere with port 53 traffic?

13

You are right, there are no ufw -- I've set it up to have port 53 and 80 open. I am able to access the web interface and query the blocks as I browse through ssh too.