FIRST - check what is going on with dnsmasq at /etc/dnsmasq.d/01-pihole.conf
.
In my case, dnsmasq/pihole-FTL wasn't starting because it was binding to a non-existent network interface. I had moved an instance from t2.micro to t3.nano. t3.nanos use the nitro hypervisor, which presents network interfaces differently. So, my primary network interface name changed from eth0
to ens5
.
Pihole's forked dnsmasq implemention is called pihole-FTL
. Just try running that (type it into the console) and see if it fixes things.
If not:
- In Ubuntu 16.04, 16.10, 18.04 and 18.10, dns is handled by
systemd-resolved
. - You can see how DNS is resolving by running
systemd-resolve --status