Forums
Windows Server 2012...
Implementing a Wind...
Troubleshooting Nam...
 
Notifications
Clear all

Troubleshooting Name Resolution on Client Computers

 
Implementing a Windows Server 2012, 2016, 2019 Network Infrastructure
1 Posts
1 Users
0 Reactions
508 Views
RSS
 mianshahzad10
(@mianshahzad10)
Member Admin
Joined: 1 year ago
Posts: 43
Topic starter 21/07/2025 10:15 am   [#23]

Clients rely on DNS to resolve hostnames like server01.company.local into IP addresses. Common symptoms of failure include inability to access internal resources, login delays, or failed nslookup results.

🛠️ Steps to Troubleshoot

  • ✅ Check DNS Settings:

ipconfig /all

  • Confirm client is using the correct internal DNS server.

  • ✅ Test Resolution:

nslookup server01
ping server01

  • If nslookup fails but ping by IP works, DNS is likely misconfigured.

  • ✅ Flush and Renew:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
ipconfig /registerdns

  • ✅ Check for Static Config Errors:
    Ensure there are no manually entered wrong DNS servers in IPv4 properties.

  • ✅ Use dcdiag /test:dns:
    On domain controllers to check DNS service health.

 

 

 

 

 

 

 



   
Quote
Forum Jump:
Next Topic  
Share: