If I specify a DNS provider when I try nslookup (nslookup google.com 1.1.1.1) then it works fine.
I was trying to install Tailscale but wasn't able to because tailscale.com couldn't be resolved. Pihole seems to be working fine otherwise. I haven't noticed problems with web browsing, streaming, torrenting and other downloading. I thought it might have been my upstream provider which was OpenDNS so I changed it to Cloudflare but the problem remains.
Details about my system:
I have Pihole installed a Pi Zero W running Bullseye, PI-HOLE V5.17.1 FTL V5.23 WEB INTERFACE V5.20.1
What I have changed since installing Pi-hole:
I installed PiVPN with Wireguard a few months ago but only used it a few times. I was trying to install Tailscale because my IP occasionally changes which breaks PiVPN.
default via 192.168.1.1 dev eth0 src 192.168.1.165 metric 202
10.216.105.0/24 dev wg0 proto kernel scope link src 10.216.105.1
192.168.1.0/24 dev eth0 proto dhcp scope link src 192.168.1.165 metric 202
PING 192.168.1.165 (192.168.1.165) 56(84) bytes of data.
64 bytes from 192.168.1.165: icmp_seq=1 ttl=64 time=0.371 ms
64 bytes from 192.168.1.165: icmp_seq=2 ttl=64 time=0.307 ms
64 bytes from 192.168.1.165: icmp_seq=3 ttl=64 time=0.314 ms
64 bytes from 192.168.1.165: icmp_seq=4 ttl=64 time=0.322 ms
64 bytes from 192.168.1.165: icmp_seq=5 ttl=64 time=0.236 ms
64 bytes from 192.168.1.165: icmp_seq=6 ttl=64 time=0.317 ms
64 bytes from 192.168.1.165: icmp_seq=7 ttl=64 time=0.321 ms
64 bytes from 192.168.1.165: icmp_seq=8 ttl=64 time=0.320 ms
64 bytes from 192.168.1.165: icmp_seq=9 ttl=64 time=0.323 ms
For that last one though it just kept going. I closed the ssh window when it got to icmp_seq=150
You're correct, 10.216.105.0 is used by pivpn. wg0 is the Pi's wireless interface which I don't use, I have the Pi connected via ethernet. I didn't notice that when I installed pivpn.
What does "cat /etc/resolv.conf" show?
# Generated by resolvconf
nameserver 2600:4040:219c:bd00::1
If you mean the web portal http://192.168.1.165/admin/settings.php?tab=dns I have Cloudflare selected as my upstream DNS server with 2 ticks under ipv4 and none under ipv6. I think everything else should be whatever the defaults are. Under Interface Settings I have the Recommended Setting selected. Nothing is active under Potentially Dangerous Options. Under Advanced DNS Settings, I have Never forward non-FQDN A and AAAA queries ticked as well as Never forward reverse lookups for private IP ranges. Rate-Limiting is set to block clients making more than 1000 queries within 60 sec. Neither Use DNSSEC or Conditional Forwarding are activated.
For the Pihole use this for the actual distro your using (not pihole version ).
cat /etc/os-release
for a client you can open a terminal and run "arp x.x.x.x" where the x.x.x.x is the piholes IP. If your clients are all windows machines I'm not sure if it will work or not. Its not a big deal, its just a little confirmation if it happened to resolve your pi.hole name. Its seems like its something with your resolve.conf so the PI's os-release is more important.
ok, so that's not resolving either. Lets change your resolv.conf. I suspect any changes will be overwritten on a reboot but lets try.
first back it up with:
sudo cp /etc/resolv.conf resolv.conf.bak
Then edit the original using:
sudo nano /etc/resolv.conf
use control+k to delete the lines ( repeat as needed ).
copy and paste the following and change the nameserver 192.168.0.8 to the ip of the pihole and save and exit (I'm gonna assume your familiar with nano and how to edit.)
domain net
search net
nameserver 192.168.0.8
nameserver 0.0.0.0
Give it a minute and try to do an nslookup to see it works.