nerdexam
CompTIA

SK0-005 · Question #85

A server technician is troubleshooting an issue regarding users who are not able to access a reporting server. The reporting server has a static IP address and is connected to a Windows domain. The…

The correct answer is C. Verify the DNS A record for the hostname of the server. When a server can be reached by IP but not by hostname, the problem lies with name resolution, requiring verification of the server's DNS record.

Troubleshooting

Question

A server technician is troubleshooting an issue regarding users who are not able to access a reporting server. The reporting server has a static IP address and is connected to a Windows domain. The technician attempts steps to narrow down the issue:

  • Pings the hostname but is not successful
  • Pings the IP address and is successful
  • Verifies the IP and DNS settings on the NIC card are okay

Which of the following should the technician do NEXT?

Options

  • APerform a tracert to the hostname and IP address.
  • BReboot the computer to apply security updates to the system.
  • CVerify the DNS A record for the hostname of the server.
  • DUpdate the DNS configuration on the host NIC card to localhost for lookups.
  • EPerform an ipconfig on the host to verify the IP configurations.

How the community answered

(52 responses)
  • A
    4% (2)
  • B
    13% (7)
  • C
    71% (37)
  • D
    2% (1)
  • E
    10% (5)

Why each option

When a server can be reached by IP but not by hostname, the problem lies with name resolution, requiring verification of the server's DNS record.

APerform a tracert to the hostname and IP address.

Performing a tracert would confirm network pathing, which is already implied to be working since ping to the IP address is successful; it would not directly diagnose a DNS resolution failure.

BReboot the computer to apply security updates to the system.

Rebooting the computer to apply security updates is unrelated to a specific DNS name resolution issue where IP connectivity is proven.

CVerify the DNS A record for the hostname of the server.Correct

Since pinging the IP address is successful but pinging the hostname fails, this indicates a name resolution issue. The most logical next step is to verify the DNS A record for the reporting server's hostname on the DNS server to ensure it correctly maps the hostname to the server's static IP address.

DUpdate the DNS configuration on the host NIC card to localhost for lookups.

Updating DNS configuration to localhost would only prevent proper external name resolution, worsening the problem for a client needing to resolve a server's hostname.

EPerform an ipconfig on the host to verify the IP configurations.

Performing an ipconfig is redundant as the technician has already 'Verifies the IP and DNS settings on the NIC card are okay'.

Concept tested: DNS name resolution troubleshooting

Source: https://learn.microsoft.com/en-us/windows-server/networking/dns/troubleshoot/troubleshoot-dns-client

Topics

#DNS#Troubleshooting#Name Resolution#Networking

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SK0-005 Practice