Quick troubleshooting view
IP access works, but the DNS name fails.
- Absent or incorrect DNS recording
- DNS client misconfigured
- Out-of-date DNS cache
- Test resolution
- Control the DNS of the post
- Empty Local Cache.
- Fix or create the, record DNS.
- Configure DNS vouchers on the post/DHCP.
- Correct the DNS suffix or area concerned.
Contextual technician plan
Run nslookup or Resolve-DnsName.
Resolve-DnsName server.example.local.A valid DNS answer should be returned by the expected resolver without timeout.
DNS works for this test; compare the exact failing name, suffix, cache and application context.
Check for the Well-DnsClientServerAddress.
The new and updated version of the document is available on the website of the European Commission.The command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Use ipconfig /flushdns.
ipconfig /flushdnsThe command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Ask a specific DNS server if necessary.
The exact failing name should resolve through the expected DNS server to the expected record without timeout.
If the exact name resolves correctly, compare application cache, suffix/search domain and the client or network where the failure remains.
If resolution fails or returns the wrong record, keep the queried server and answer and correct the resolver, zone/record or DNS path that is actually wrong.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Squad if several internal DNS return different answers for the same name.
IP access works, but the DNS name fails.
Causes probables
- Absent or incorrect DNS recording
- DNS client misconfigured
- Out-of-date DNS cache
- Invalid DNS Suffix
- Incomplete DNS replication
Diagnostic étape par étape
- 1
Test resolution
Run nslookup or Resolve-DnsName.
- 2
Control the DNS of the post
Check for the Well-DnsClientServerAddress.
- 3
Empty Local Cache.
Use ipconfig /flushdns.
- 4
Compare multiple DNS.
Ask a specific DNS server if necessary.
Commands utiles
Resolve-DnsName server.example.local.The new and updated version of the document is available on the website of the European Commission.ipconfig /flushdnsSolutions possibles
- Fix or create the, record DNS.
- Configure DNS vouchers on the post/DHCP.
- Correct the DNS suffix or area concerned.
Squad if several internal DNS return different answers for the same name.