Your nslookup results show that the machine you run those from doesn't use Pi-hole for DNS, but rather a local stub resolver at 127.0.0.53.
That stub resolver also doesn't forward DNS requests to Pi-hole upstream, or else it would have returned your Pi-hole's IP instead of NXDOMAIN.
But judging by your prompt (pilothobs@NUC-8i), it would seem you ran those nslookups from your Pi-hole host, when I asked you to run them from a client.
If that's indeed your Pi-hole host, then its DNS resolution would be irrelevant for Pi-hole's DNS operation. It would be ok and can even be of advantage that Pi-hole's host would be using a public DNS server.
Now let's take a look at your Windows client, which you've now also provided results for:
Your Windows nslookup results show that your Windows client is using your machine at 192.168.1.1 for DNS (your router, presumably), which in turn did not use Pi-hole as upstream, as obvious by that NXDOMAIN.
You should verify your router settings again.
Make sure you did configure your router to distribute your Pi-hole host machine's IPv4 via DHCP, and also check the lease validity - routers may hand out DHCP leases valid for days.