DC cannot ping its client computer by Hostname but it can ping by IP address

Question

I have limited experience with Windows server and Domain controller, so thank you for being patient with me.
I search on this forum but not quite find the correct answer to my case either. Here is my sitution:

1/ Windows Server 2019 Std version, running Domain controller and DNS server name DC-01 in the Office on 192.168.100.0/24 network
2/ A desktop (name DSKT-01) running Windows 10 Pro at Home-Office on 10.10.100.0/24 network
3/ The Office and Home is Site-to-Site VPNed.
4/ The DSKT-01 joined the DC-01 all good.

Few days ago, I needed to reinstall the Desktop, then name it the same as previously (DSKT-01). But somehow it has lost the connection to DC-01. I then removed the "previous" DKST-01 computer from DC-01 Active Directory; Created the new computer and name it the same DSKT-01. Then from the DSKT-01, I can rejoined the DC-01 successfully.

However, from the DC-01, I can't ping the Desktop using its hostname as DKST-01 (was OK before the reinstallation). I can however, ping the DSKT-01 by its IP address. Everything else works except pinging the name. It said host (DSKT-01) cannot be found.

A/ What I have done:

A.1/ Delete the dns cache (ipconfig /flushdns) from both DC-01 and DSKT-01
A.2/ Update policy (gpupdate /force) on both machines
A.3/ Delete the contain of host file on DC-01 and DSKT-01

B/ Other notes:

B.1/ When I checked in the DNS server, in the Forward lookup zone, there is a record of the DSKT-01's IP address which is automatically created when joining the DKST-01 to the DC-01. But still, I cannot ping the client PC by its hostname. This bug me the most, especially it was working previously and after the reinstall, it stops

B.2/ DC-01 can ping other client computers in the same network using their Hostname.

B.3 / Other client computers in the same network with the DC-01 can ping the DSKT-01 by it hostname.

Why the DC-01 cannot ping its client "DSKT-01" by its hostname?

Anyone have any idea what I may be missing?

Thank you very much

Answer 1

This solve the problem:

• Delete the computer in the Domain controller and make sure no record was left behind in the DNS forward lookup zone. Restart DC
• Disjoin the client to the domain, restart the client
• Join the client to DC again.
• Check the DNS setting in the DC: If virtualization is employed, under the the virtual NIC (created by Hyper-V) where applicable to your DC/AD, one of the DNS server will have to be the DC itself (either IP address or loopback address 127.0.0.1) so that it will resolve the internal computer hostnames. The other DNS could point to other DNS server (to PiHole server in our case).
• So, DNS1: the DC
• DNS 2: Pi-hole server

Now it works again!

Answer 2

Please run;

Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\problemworkstation.txt

then put unzipped text files up on OneDrive and share a link.

Answer 3

@Anonymous : Do you want me to run these commands in the Windows Server 2019 or in the client computer?

Answer 4

Each domain controller and the problem member.

Answer 5

@Anonymous :
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
Are they the same?