🟠 High   ⏱ 5–30 min  Last verified: 29 May 2026
Affected versions: Windows Server 2012 R2

📖 ~1 min read

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution — Primary Fix
  7. Solution — Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

Name lookups intermittently fail, breaking package downloads and API connectivity.

Environment & Reproduction

Windows Server 2012 R2 with stale or unreachable DNS forwarders.

Resolve-DnsName microsoft.com
Get-DnsClientServerAddress

Root Cause Analysis

Configured resolvers are unreachable or recursion path is blocked by firewall policy.

Quick Triage

Test direct query to each configured resolver and check response times.

Test-NetConnection 8.8.8.8 -Port 53
Resolve-DnsName github.com -Server 1.1.1.1

Step-by-Step Diagnosis

Review DNS cache state, server settings, and timeout events.

ipconfig /displaydns
Get-WinEvent -LogName 'DNS Server' -MaxEvents 80
Illustrative mockup for windows-server-2012-r2 — terminal_or_powershell
DNS timeout troubleshooting — Illustrative mockup — Progressive Robot

Solution — Primary Fix

Set reachable DNS servers and flush resolver cache.

Still having issues? Our Network Design team can diagnose and resolve this for you. Get in touch for a free consultation.

Set-DnsClientServerAddress -InterfaceAlias Ethernet -ServerAddresses 1.1.1.1,8.8.8.8
ipconfig /flushdns
Illustrative mockup for windows-server-2012-r2 — event_or_log_viewer
DNS server timeout events — Illustrative mockup — Progressive Robot

Solution — Alternative Approaches

Deploy internal recursive resolver with monitored forwarders.

Add-DnsServerForwarder -IPAddress 9.9.9.9

Verification & Acceptance Criteria

Lookups resolve consistently with acceptable latency.

Resolve-DnsName powershellgallery.com
nslookup microsoft.com

Rollback Plan

Restore previous resolver list if split-horizon requirements are impacted.

Set-DnsClientServerAddress -InterfaceAlias Ethernet -ResetServerAddresses

Prevention & Hardening

Monitor resolver health and alert on prolonged query failures.

Get-DnsClientCache | Measure-Object

Related to TLS handshake failures and proxy connection errors.

Related tutorial: View the step-by-step tutorial for Windows Server 2012 R2.

View all Windows Server 2012 R2 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft DNS client troubleshooting and resolver best practices.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.