NSLookup Unable To Resolve Local Computer's Hostname

I went through all of the suggestions here: Windows unable to resolve hostnames

I recently discovered that I cannot resolve any Windows host name (i.e., the computer name). For example, if open a command prompt (all machines run Windows 10 Enterprise 64-bit) and enter NSLOOKUP TEMP, I receive the message: *** router.asus.com can't find TEMP: None-existent domain.

I can PING -a 192.168.3.101 (the static-IP of my desktop computer), and that's not only successful but also reports the correct host name TEMP while doing so.

What could be the broken link here that's preventing NSLookup from being able to resolve the name TEMP?

P.S. My ethernet adapter's properties point to my router's gateway as the primary DNS: 192.168.3.1. I can do an NSLookup on external internet sites successfully, such as msn.com.

So like in the thread before your router most likely isn't your DNS server its just proxy which forward your requests to real DNS server somewhere else. So if DNS server outside would try to resolve your pc hostname to ip address it's just impossible because:

• hostnames are not unique in global scale unlike website names with top-level domain like .org so there could be 100 000 PCs with TEMP name with 100 000 different IP addresses

If you really want that your setup will work with resolving local hostnames you need to create your own DNS server for example as a service on Windows Server then if you will point your DNS queries to this local DNS server then it should work.