Newly installed PiHole w/ Unbound and enabled DHCP not working on all devices

[ecterun]

Expected Behaviour:

Just set up the PiHole on a Pi Zero 2W, disabled DHCP on my router, and enabled DHCP in Pi Hole. I am expecting to have my PC running windows 10 to use the Pi-Hole but it seems to be bypassing it. I am seeing adds, as well as when i run nslookup pi.hole i dont get my dns.

Actual Behaviour:

_Windows 10 PC is not connecting to Pi-hole.

When i run nslookup pi.hole I get

Server: dsldevice6.attlocal.net
Address: 2600:1700:25b8:5020::1

Non-authoritative answer:
Name: pi.hole
Address: 23.202.231.169_

Another raspberry pi device seems to be using my router as the dns server, i dont know if this is intended or not.

Server: 192.168.1.254
Address: 192.168.1.254#53

Non-authoritative answer:
Name: pi.hole
Address: 23.202.231.169

Debug Token:

6Bt92vkI

[Bucking_Horn]

Both the IPv6 and the IPv4 addresses belong to your router.

A successful resolution of pi.hole indicates that your router is using Pi-hole as its upstream DNS server.

In such a scenario, Pi-hole's receives only DNS requests originating from your router (and itself), so you won't be able to attribute DNS requests to individual clients and thus can't make use of client-based filtering.

As long as Pi-hole is your router's only upstream DNS server, this is a valid configuration: Your clients talk to your router for DNS, and your router forwards those to your Pi-hole, effectively still filtering all DNS traffic.

[ecterun]

ok, that makes sense. But i feel I may still have something configured incorrectly here as i added a DNS record which will show up on some of my other raspberry pi devices when i do a nslookup. But it seems my Windows 10 device can not find them.

Windows 10 Test:
nslookup fluiddpi.lan
Server: dsldevice6.attlocal.net
Address: 2600:1700:25b8:5020::1

*** dsldevice6.attlocal.net can't find fluiddpi.lan: Non-existent domain

Raspberry Pi OS device
nslookup fluiddpi.lan
Server: 192.168.1.196
Address: 192.168.1.196#53

Name: fluiddpi.lan
Address: 192.168.1.51

It seems my windows machine is going to my router's DNS while the pi os is going directly to the pi-hole. I have disabled DHCP 4 and 6 on my router, as well as ran ipconfig flushdns and registerdns on the windows machine.

If this is to far removed from my initial post let me know and i can create a new post.

[ecterun]

just a little more information to hopefully help from the windows pc. Here is the output from ipconfig /all for the connection

Ethernet adapter Ethernet 3:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller #2
Physical Address. . . . . . . . . : 3C-7C-3F-25-C5-5F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2600:1700:25b8:5020::44(Preferred)
Lease Obtained. . . . . . . . . . : Thursday, December 9, 2021 10:02:31 AM
Lease Expires . . . . . . . . . . : Friday, January 7, 2022 11:00:40 PM
IPv6 Address. . . . . . . . . . . : 2600:1700:25b8:5020:d459:16af:f8b0:4b02(Preferred)
Temporary IPv6 Address. . . . . . : 2600:1700:25b8:5020:40d5:94a4:c87b:6ccb(Preferred)
Link-local IPv6 Address . . . . . : fe80::d459:16af:f8b0:4b02%5(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.213(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, December 9, 2021 10:02:32 AM
Lease Expires . . . . . . . . . . : Friday, December 10, 2021 10:02:32 AM
Default Gateway . . . . . . . . . : fe80::de8d:8aff:fe7c:2f92%5
192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.196
DHCPv6 IAID . . . . . . . . . . . : 440171583
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-E6-FC-91-3C-7C-3F-25-C5-5F
DNS Servers . . . . . . . . . . . : 2600:1700:25b8:5020::1
192.168.1.196
2600:1700:25b8:5020::1
2600:1700:25b8:5020:a65:4ff8:4a61:a6b0
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
attlocal.net
attlocal.net