.local LAN name problems, a new bug in Windows 10 1809 - 17763.55 ?

Brass Contributor

In new windows version 1809 (Build 17763.55), when i ping a name of local network computer sometimes it adds a  .local to the end of the name.





Because of this some programs display error message that XRS.local doesn't exist in local network, but XRS does.


Is there a way to turn off .local suffix at the end of computer name ? or is this a new 1809 bug ?

This does not happen in Windows 10 1607. 1607 never displays .local in ipv6 SMB names.

If i turn on only IPV4 .local never appears, same happens if i disable multicast DNS, .local never appears only full name of PC.


Same happens with Windows Server 2019 version 1809 (Build 17763.55), it always adds .local to the end of computer name.


How to reproduce:

1. Install Windows 10 1809 or Windows Server 2019 trial on PC1

2. Install Windows 10 1809 or Windows Server 2019 trial on PC2

3. Connect 2 PC's via switch / or via virtual network / virtualbox

4. Ping PC2 from PC1 or tracert PC2 from PC1

5. PC2 will have it's name changed to PC2.local 





7 Replies

This is likely coming from mDNS.  Do you have an mDNS responder installed ( like Apple's Bonjour?)

Since 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]
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
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?
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)
No, nothing was installed or added, only clean install of windows.

Windows IP Configuration

Host Name . . . . . . . . . . . . : XRS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Server Adapter I350-T4


DNS Suffix is nothing as you can see.

I have the same issue as well. Disabled Apple Bonjour service and it seems to work again. But I'm not entirely sure it's related, because I re-enabled the service and it is still working for me.