Yes I can, but it can be complicated to explain….
I assume you are using a Windows client…. (or you would have found out the reason already)
Your WDHD's hostname is passed to the DHCP-server of your network. Often this DHCP-server co-operates with the DNS-server on the same machine. This DNS-server will take the hostname and glues the local domain name of your network to it. Sometimes it is empty.
So your WDHD really has nothing to do with the mechanism to convert a hostname to its IP-address. It's your DNS-server and how well it works together with the DHCP-server. If they don't co-operate (maybe they are on different machines) it's impossible to determine the address of that hostname…
I can tell you a trick to test which hostname can be used. Just go to your Windows prompt and give the command:
If your DNS-server is properly configured, it can tell you the WDHD's name..
If it doesn't you will have to change your network-setup (not drastically most of the time)
If you give me an "ipconfig /all" of your network and tell me which machines those IP's represent I can tell you who or what's at fault.