Expected Behaviour:
I am using a Jetson Nano running Ubuntu 18.04.6 LTS with a static IP address. The nano is connected to the network using a ethernet cable. I got pihole up and running by using the docker image and instructions from docker-pi-hole. Because I am running on Ubuntu, I ran into the issue of port 53 being already in use by systemd-resolved. I got around that by following the steps mentioned on the Installing on Ubuntu section which asks me to run the following commands:
sudo sed -r -i.orig 's/#?DNSStubListener=yes/DNSStubListener=no/g' /etc/systemd/resolved.conf
sudo sh -c 'rm /etc/resolv.conf && ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf'
systemctl restart systemd-resolved
As a result of these steps, I am able to start the pihole container.
Actual Behaviour:
Once I start the container, I am able to access the pihole website. Once I change the settings on my router to use the pihole as the DNS, my Nano (running the pihole container) can no longer connect to the internet. Interestingly, pihole seems to be functioning properly, which means I see requests from other devices on the network coming in, being allowed or blocked based on the gravity list. Only the nano itself cannot connect to the internet.
Result of ping 1.1.1.1:
$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
^C
--- 1.1.1.1 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6149ms
Result of route (router's LAN IP is 192.168.0.1)
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default _gateway 0.0.0.0 UG 20100 0 0 eth0
link-local 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.18.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-a7381256f38d
192.168.0.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0
Contents of /etc/resolv.conf:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 1.1.1.1
nameserver 192.168.0.193
nameserver 192.168.10.254
The 1.1.1.1 nameserver is in there because I changed /etc/systemd/resolved.conf to:
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details
[Resolve]
DNS=1.1.1.1
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#Cache=yes
DNSStubListener=no
hoping that having 1.1.1.1 as the nameserver might solve issues. No luck.
If i remove the pihole server as the DNS, the nano is able to connect to the internet again, though of course nothing's using pihole anymore. I've been trying to solve this issue looking at other topics, but no luck as well. Can't seem to figure out what I'm doing differently that leads to issues.
Debug Token:
Can't run pihole -d cause no internet on the pihole server.
.