Why is the computer's domain name not resolved?

Question

Computer networks

Hello, tell me what could be the problem, there is a domain with an AD server on Windows 2012, there are a number of computers in the domain, the computers are approximately the same, Win 8.1 was installed on them from one disk, the computers were entered into the domain, they work fine in the domain, i.e. . group policies are applied to them equally normally, outlook accepts mail using the user's domain account and all that, but as it turned out, some computers on the network are unavailable by name, and only some and not all, i.e. they don’t even ping by domain name, although they ping by ip, and even on this very computer, which is not available on the network by name, it even itself in the cmd console at its home. It cannot ping the name, it cannot resolve the name, in the file hosts is fine. just like on all other computers, all the necessary services are enabled - DNS Client, TCP / TP NetBios Assistant,
performed network and DNS cache reset on problem computers:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
Rebooted, didn't help, nothing changed

Answer 1

Most often I meet such a picture if the DNS is configured incorrectly on the clients and on the server. Look in the settings of network adapters on client PCs - who is registered as a DNS server? Probably anything is written there, for example 8.8.8.8, but not the right address - the address of your dns server. There must be he and ONLY he! If there are several DCs, then of course there are several addresses. If other DNS servers are registered there, say Yandex, then how can Yandex know your internal addresses in your network?
Also, if the addresses were assigned manually, then it would be good to specify the DNS connection suffix. If the suffix is ​​not specified, then the computer may not find anything at the request of pc03, and if specified, it will first try to find pc03.mylan.local and, most likely, will find it.
On the server side, it is necessary that the server itself (127.0.0.1) is also registered in the DNS in the network adapter settings. Well, then we are already looking at the settings of the DNS server service if something is wrong.
If you use dhcp, then the dhcp server must be authorized in the domain so that its records get to the dns server. If you do not use and prescribe addresses with your hands, then write these ip / hostname in dns as well.
As a diagnostic tool, use nslookup - a great thing that allows you to immediately identify a bunch of problems instead of blindly poking.