Pi Hole not resolving local DNS

Help
1

I having been using pihole for awhile now but I have been experiencing issues with DNS resolution recently. Pi.hole and and local records that I put in the pihole GUI are resolving. The forwarder is working like normal. When I run nslookup on a client I get

Server: DietPi
Address: (pi hole ip)

*** DietPi can't find pi.hole: Non-existent domain

I get the same error when trying to resolve any records that I entered manually

https://tricorder.pi-hole.net/Y81lIJmp/

Any help is appreciated.

2

A few things from your debug log.

It doesn't look like you have global IPv6 connectivity:

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] No IPv6 address available on lo
[✓] No IPv6 address available on eth0
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

So setting a remote IPv6 address for an upstream will not work:

-rw-r--r-- 1 pihole pihole 55K Jul  8 22:02 /etc/pihole/pihole.toml
   [dns]
     upstreams = [
       "94.140.14.14",
       "94.140.15.15",
       "2a10:50c0::1:ff",
       "2a10:50c0::2:ff"
     ] ### CHANGED, default = []

I only see one entry:

     hosts = [
       "192.168.7.153 wi****.mc***.w***"
     ] ### CHANGED, default = []

What is the exact nslookup command you are entering?

The server running Pi-hole looks like it is being assigned an IP address via DHCP from the router(?) at 192.168.7.1:

   * Received 302 bytes from 192.168.7.1 @ eth0
     Offered IP address: 192.168.7.6
     Server IP address: 192.168.7.1

that same DHCP server is not advertising Pi-hole as the DNS server:

      ntp-server: 192.168.7.253
      dns-server: 208.67.220.220
      dns-server: 208.67.222.222
      router: 192.168.7.1

The clients shown on the log snippet are from a different subnet:

   Jul  8 22:17:02 dnsmasq[18945]: query[A] <redact>.com from 192.168.6.132

192.168.6.0/24 is not on 192.168.7.0/24:

   2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000

       inet 192.168.7.6/24 brd 192.168.7.255 scope global dynamic eth0
3

For the IPv6, I am using ipv4 mostly for my internal network. I just put the addresses there, but I can remove them.

For the entry, I had more in there but when I was troubleshooting I just kept the one local record. The command I am using to test is

nslookup win***.mc***.w***

Just to give more insight, I am running multiple vlans on my internal network. So a machine on 192.168.6 or .2 isnt going to be on the same network. I have done some more troubleshooting and I have another machine on a different vlan that has no issue resolving. It is a MAC and I am having my issues on a windows.

On the vlan that the pihole server is on, the dhcp server is advertising a different DNS but that deals with the way that my network is setup. Other servers dont need to use the pihole as their DNS. I am not sure that would make a difference when it comes to the local resolution for the devices that are using the pihole as their DNS