nslookup results:
C:>nslookup google.com 192.168.1.24
Server: raspberrypi.lan
Address: 192.168.1.24Non-authoritative answer:
Name: google.com
Addresses: 2a00:1450:400b:c01::71
2a00:1450:400b:c01::65
2a00:1450:400b:c01::64
2a00:1450:400b:c01::8a
74.125.193.101
74.125.193.102
74.125.193.100
74.125.193.138
74.125.193.139
74.125.193.113
I'm assuming you meant Pi-hole IP (192.168.1.24). If so the results are as follows:
C:>nslookup google.com
Server: raspberrypi.lan
Address: 192.168.1.24Non-authoritative answer:
Name: google.com
Addresses: 2a00:1450:400b:c01::8a
2a00:1450:400b:c01::64
2a00:1450:400b:c01::65
2a00:1450:400b:c01::71
74.125.193.113
74.125.193.139
74.125.193.138
74.125.193.100
74.125.193.102
74.125.193.101
C:>nslookup flurry.com
Server: raspberrypi.lan
Address: 192.168.1.24Name: flurry.com
Addresses: ::
0.0.0.0
C:>nslookup pi.hole
Server: raspberrypi.lan
Address: 192.168.1.24Name: pi.hole
Address: 192.168.1.24
I was using "ipconfig /release" and "ipconfig /renew" to ensure I was getting a new lease between config changes to the ISP router or the Pi-hole.