C:\WINDOWS\System32>nslookup pi.hole
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.51
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
C:\WINDOWS\System32>nslookup pi.hole 192.168.1.51
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.51
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
I can however access the PiHole admin panel from Windows via pi.hole/admin as well as the IP above.
That's the problem. The router (DHCP Server) is sending itself as a DNS server. Windows will use both DNS servers, there is no primary and secondary or backup DNS servers.
A number of routers will hardcode themselves as DNS servers when you set them up for DHCP servers. I don't see any option to disable that in your router, you may have to use the DHCP server in Pi-hole instead, this situation is the reason we went with that feature for Pi-hole.
Thought about Merlin, wasn't sure the pros/cons of using PiHole vs Router as the DHCP server.
Tried setting up the DHCP on the PiHole and when I try to add a static lease I get this..
Error
There was a problem applying your settings.
Debugging information:
PHP error (2): fopen(/etc/dnsmasq.d/04-pihole-static-dhcp.conf): failed to open stream: No such file or directory in /var/www/html/admin/scripts/pi-hole/php/savesettings.php:84
Seems to have added the new static IP tho, just a weird error?
Yep that seems to match, added a second one and no error.
Is it normal to have a different IP in the DHCP leases for the PiHole (showing 192.168.1.75) even though I have a Static DHCP lease for the PiHole (192.168.1.51)? Both seem to resolve to the PiHole, I just figured they would be the same?
I'm still noticing the Connection Reset error page on calling a page, right before it auto reloads and actually loads the site.. disabled Wifi on the PiHole and haven't seen the issue so far.. let's hope it's resolved, otherwise any ideas what it may be?
Update: Same issue with connection reset appearing still
This is sounding like a client issue. Is this only with that browser, and only on that client? Or is this with all browsers on that client, or all browsers on all clients?