Forum Discussion
Windows Server 2019 - 1809 - Build 17763.107 - LAN names return .local
In Windows Server 2019 - 1809 - Build 17763.107 when user pings or tracert ( trace routes ) a LAN name, name has 50% chance to return .local at the end. Example: How to reproduce: 1. ...
Dusty Harper
Microsoft
MicrosoftThis is likely coming from mDNS. Do you have an mDNS responder installed ( like Apple's Bonjour?)
Dusty HarperMicrosoft
MicrosoftSince WinXP Name Resolution occurs in the following order
1) Is the name referring to the localhost? [Local Cache lookup]
2) Is the name in %WinIdr%\System32\Drivers\etc\Hosts? [Hosts lookup]
3) Is the name in the local DNS cache? [DNS cache]
4) Can a DNS server resolve the name? [DNS Query]
1) Is the name referring to the localhost? [Local Cache lookup]
2) Is the name in %WinIdr%\System32\Drivers\etc\Hosts? [Hosts lookup]
3) Is the name in the local DNS cache? [DNS cache]
4) Can a DNS server resolve the name? [DNS Query]
All of these are configurable via the Services\TCPIP\ServiceProvider regkey
After this it gets a bit more convoluted and you need to see how your device is configured
Perform Ipconfig /all and at the top look for Node Type
Perform Ipconfig /all and at the top look for Node Type
You are most likely using H(ybrid) Node Name Resolution
5) Is the name in the NetBIOS cache? [NetBIOS cache]
6) try P(eer)-Node Resolution
a) Can a WINS server (if configured) resolve the name? [WINS Query]
b) Is there an answer to the name using mDNS (multicast DNS)?
c) Is there an answer to the name using LLMNR (Link Local Multicast name Resolution)?
7) Try B(roadcast)-Node Resolution
a) Is there an answer to the name using NetBIOS broadcast?
5) Is the name in the NetBIOS cache? [NetBIOS cache]
6) try P(eer)-Node Resolution
a) Can a WINS server (if configured) resolve the name? [WINS Query]
b) Is there an answer to the name using mDNS (multicast DNS)?
c) Is there an answer to the name using LLMNR (Link Local Multicast name Resolution)?
7) Try B(roadcast)-Node Resolution
a) Is there an answer to the name using NetBIOS broadcast?
This behavior is configurable via the Services\NetBT\Parameters\NodeType & Services\NetBT\Parameters\DHCPNodeType
What I suspect is happening is that you are using a short name (no DNS suffix specified, and the DNS query is taking too long to return, so other methosds are tried, and either mDNS or LLMNR is able to answer (hence the .local suffix)
Something you should check is in your TCPIP properties, what DNS suffix are you appending to your short names? (you can find this using Ipconfig /all)