A user is unable to connect to the company's 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?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The user in the scenario is able to connect to the company's intranet server by IP address but not by Fully Qualified Domain Name (FQDN), which indicates that there might be a DNS resolution issue.
The fact that the user can successfully ping the server by IP address and can properly resolve the FQDN using nslookup indicates that the problem is most likely not with the client's DNS resolver or the DNS server.
Since other users are not having the same issue, it's possible that there is a local configuration problem on the affected user's system.
The first step in troubleshooting this issue would be to check the hosts file, which is a local file on the user's computer that maps hostnames to IP addresses. It's possible that the hosts file contains an incorrect entry for the server in question or that it is missing altogether.
Therefore, the next step that the administrator should take is to examine the hosts file (option D) on the affected user's computer to ensure that it does not contain any incorrect entries. If the hosts file is missing or contains incorrect entries, it should be corrected or restored.
If examining the hosts file does not resolve the issue, the administrator may consider other options such as examining the lmhost file (option A) or flushing the cache on the DNS server (option B) as a last resort. However, since the issue is localized to only one user, it is unlikely that the DNS server or the WINS server cache (option C) is causing the problem.