The first thing you should look for and this is usually the culprit is a duplicate IP address on the network. Usually you can spot these by simply looking on your DHCP server for "BAD_ADDRESS".
Is it possible that the server is simply overloaded at times?
When NLA starts to detect the network location, the machine will contact the domain controller via port 389. If this detection successful, it will get the domain firewall profile (allowing for correct ports) and we cannot change the network location profile.
If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.
So I'd check the domain controller and problem client have the static address of DC listed for DNS and no others such as router or public DNS
Similar discussion here https://social.technet.microsoft.com/Forums/windowsserver/en-US/3711b370-af03-4916-9356-096d68649d64/server-loses-connection-with-domain-dns-issue?forum=winserverNIS
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–