SK0-003 · Question #232
A user is unable to connect to the companys intranet server by FQDN, but can connect by IP address. Other users are not having a problem. An administrator verifies that the user can successfully…
The correct answer is D. Examine the hosts file. Since nslookup can resolve the FQDN and ipconfig /flushdns didn't fix the issue, the next step to troubleshoot a single user's inability to connect by FQDN is to examine the local hosts file.
Question
A user is unable to connect to the companys intranet server by FQDN, but can connect by IP address. Other users are not having a problem. An administrator verifies that the user can successfully ping the server by IP address and can properly resolve the FQDN using nslookup. The problem is persisting after running ipconfig /flushdns. Which of the following should the administrator do NEXT?
Options
- AExamine the lmhost file.
- BFlush the cache on the DNS server.
- CFlush the cache on the WINS server.
- DExamine the hosts file.
How the community answered
(22 responses)- A5% (1)
- B14% (3)
- C5% (1)
- D77% (17)
Why each option
Since `nslookup` can resolve the FQDN and `ipconfig /flushdns` didn't fix the issue, the next step to troubleshoot a single user's inability to connect by FQDN is to examine the local `hosts` file.
The `lmhosts` file is used for NetBIOS name resolution, which is not typically the mechanism used for connecting to an intranet server by its Fully Qualified Domain Name (FQDN).
Flushing the cache on the DNS server is unnecessary because `nslookup` already confirmed that the DNS server is correctly resolving the FQDN, indicating the issue is on the client side.
Flushing the cache on the WINS server is irrelevant because WINS (Windows Internet Name Service) is used for NetBIOS name resolution, not FQDN resolution which relies on DNS.
The `hosts` file is a local text file that maps hostnames to IP addresses and is consulted before DNS queries; if it contains an incorrect or outdated entry for the intranet server, it will override the correct DNS resolution shown by `nslookup` and prevent connection for that specific user.
Concept tested: Name resolution troubleshooting order
Source: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/order-of-dns-host-name-resolution
Topics
Community Discussion
No community discussion yet for this question.