Forum Discussion
Issues/Problems with Release 17733
Well, the last issue I was having with Server 2019 seems to have been solved or at least I have a work-around. That issue was that with Server 2019 having it's
IPv4 address on a Private network, and trying to reach our other Servers/Workstations, etc. on a Public IPv4 network, I could not use the single name of the server (LLMNR resolving to an IPv6 FE80 address) - it would not resolve as it always had with Server 2012 and Server 2016.) I want to emphasize that the Server 2019 has NO DNS Suffix configured!!!!!. To make the resolution work, I had to add the period after the single name, and it then resolved with the single name. Normally in the past the period only had to be used with the machine had a DNS suffix configured that was not resolvable by the DNS Server it was pointed to and we wanted to revert to only signal name lookup. What lead me to this "fix" was another person noting that when he pinged addresses by name the ".local" suffix was being added automatically (at times, not always) to the name, even when he had no suffix configured!!!!! At any rate, now my students can still do the lab projects by just adding the "period" after the LLMNR name!!!!
I don't think this is necessarily new. This one may be helpful in that regard.
https://serverfault.com/questions/74067/windows-appending-domain-suffix-to-all-lookups
Well, the "Period" fix did not work after all for LLMNR not working with IPv6. When doing the lab project in class it did not work for the students. However, installing the January 18, 2018 cumulative update for Server 2019 seems to definitely have fixed the problem. We ill be doing some further testing, however - I'm not believing anything until we try it on some 20 to 30 machines!!!! That description of the update mentioned a fix for IPv4/IPv6 - not this problem however - but whatever they fixed seemed to take care of LLMNR working with only IPv6 enabled.