FIRST - check what is going on with dnsmasq at
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
Pihole's forked dnsmasq implemention is called
pihole-FTL. Just try running that (type it into the console) and see if it fixes things.
- In Ubuntu 16.04, 16.10, 18.04 and 18.10, dns is handled by
- You can see how DNS is resolving by running