Windows 11 & Pi Hole local dns problems - cannot resolve by hostname?

Hello! I am having a problem with the pi hole and my windows clients, they cannot reach local devices on my network by hostname. To make things weirder, 'nslookup' returns the correct response then proceeds to fail directly afterwards as soon as I try again using ping or the web browser.

Please see this screenshot:

I have gone into Local DNS -> DNS Records and manually assigned each entry and made sure there's no typos or anything weird, and it still is not working.

What is the problem here? Also regular clearweb requests seem to all be going through the Pi Hole with no issues as everything is blocked and those queries show up in the Query Log - but the failed local ones do NOT!

Thanks for any help

ping is using additional means to resolve hostnames, not just DNS.
On Windows, ping sometimes has to be coaxed into using DNS by appending a dot to the hostname, e.g. ping router..

In addition, your client may be aware of alternative DNS servers, by-passing Pi-hole, and thus failing resolution of hsitnames defined in your Pi-hole.

Run from a Windows client, check the DNS server section of

ipconfig /all

In some cases You may need to force Windows to clear/refresh the local DNS cache:

IPCONFIG /RELEASE
IPCONFIG /FLUSHDNS
IPCONFIG /RENEW

That should eliminate the local cache related fails...

Thanks for the replies! The ipconfig /commands wouldn't do anything I assumed because this is an old problem that has persisted through many reboots, and I assume those would be issued each time after a reboot when the network connects? Or would I STILL need to issue those manually even after multiple reboots?

The period thing, however, DID work. It's annoying, though! I wonder why that's required and won't work without it?

Thanks for your assistance

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.