Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.
**
EDIT: Basic confusion. DHCP Lan DNS cannot be changed on this, so it’s using WAN to forward it. This means it still works, it just can’t distinguish the individual devices connected to my main router for the admin panel on pi-hole.**
Expected Behaviour:
Replace this text with what you think should be happening. Please include as much detail relevant to your system/install as possible including, but not limited to:
Running a Raspberry Pi 5 with Raspberry Pi OS, according to the debug log it’s Debian Version 12 (aarch64). Basically the OS that comes installed on the MicroSD.
I’m quite new to networking so I apologize in advance if what I’m trying to convey is not making sense. To preface, as it stands PiHole does seem to be working. My issue is I’m just trying to understand why it’s using 100.100.100.100 or 192.168.1.1 when doing a command such as nslookup or dig. I would just like to confirm if everything looks okay and I did my configuration right 
What should be happening is that it will return 127.0.0.1. In the PiHole admin portal it also doesn’t show very many queries from localhost. A lot of queries come from 192.168.1.1 and I’m just not sure if this is something to be concerned about or not. What it sounds like is that 100.100.100.100 just forwards all traffic to the DNS configured on Tailscale.
Actual Behaviour:
I started by configuring my PiHole and Unbound together, I set up the PiHole using sudo curl -sSL ``https://install.pi-hole.net`` | bashI ran through the set up. During the set up I set a static IP (192.168.1.254) on my router’s local DHCP server for my PiHole, another noteworthy part was where it asked me to choose an interface, which I chose wlan0 because my Pi is not set up with ethernet (eth0). Then I went to set up Unbound, I installed Unbound using sudo apt install unboundthen I followed the PiHole Unbound documentation to create pi-hole.conf. I configured it exactly the same as the documentation shows on Unbound, I did the DNSSEC validation and it was the same answers as the configuration. Then I accessed my PiHole admin panel and added 127.0.0.1#5335 as a custom DNS upstream server. I saved, exited, and restarted PiHole and the Pi itself for good measure. With those two configured correctly I moved on to Tailscale, which I had setup the day prior but had not connected to my Pi quite yet. Before getting PiHole set up, I had been using NextDNS. After downloading Tailscale using curl -fsSL ``https://tailscale.com/install.sh`` | sh I ran sudo tailscale up --accept-dns=false and signed in which added my Pi to my Tailnet. I also happened to disable key expiry, and I made my Pi an exit node for my Tailnet. Then I configured my PiHole to be the DNS server for my Tailnet, setting the DNS to the Tailscale IP for my Pi (100.x.y.z). I was sure to set this to Override DNS Servers as well. I restarted all three services again for good measure, PiHole seemed to be blocking things and still is. I then configured this to my router on the DHCP Lan server using 192.168.1.254 as the Primary DNS. Rebooted my router for this to take effect across the network. Decided to do some testing to see if everything was in working order, so I did nslookup google.com which returned Server: magicdns.localhost-tailscale-daemon Address: 100.100.100.100.I don’t know what changed but it would also return Address: 192.168.1.1. Doing nslookup 127.0.0.1 on the Pi host returns 1.0.0.127.in-addr.arpa name = localhost and appears in the PiHole query log from client pi.hole. On my Windows machine which if on the Tailnet when I do nslookupit will return Default Server: magicdns.localhost-tailscale-daemon Address: 100.100.100.100. If I disconnect from the Tailnet and I run nslookup it returns Default Server: UnKnown Address: 192.168.1.1