nerdexam
CompTIA

SK0-004 · Question #892

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. Pinging by IP succeeds but pinging by hostname fails, isolating the problem to DNS name resolution rather than network connectivity.

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

(22 responses)
  • A
    14% (3)
  • B
    5% (1)
  • C
    77% (17)
  • E
    5% (1)

Why each option

Pinging by IP succeeds but pinging by hostname fails, isolating the problem to DNS name resolution rather than network connectivity.

APerform a tracert to the hostname and IP address.

A tracert provides routing path information but does not help resolve a DNS A record misconfiguration, which is already identified as the likely cause.

BReboot the computer to apply security updates to the system.

Rebooting to apply security updates is unrelated to a DNS name resolution failure and does not address the missing or incorrect A record.

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

Because IP-based connectivity is confirmed and the NIC DNS settings are verified, the fault must be in the DNS server itself - specifically a missing or incorrect A record that maps the server's hostname to its static IP address. Verifying the DNS A record is the direct next step to confirm and fix the name resolution failure.

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

Setting DNS to localhost would break all external DNS resolution entirely and would not fix the A record on the authoritative DNS server.

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

IP configuration on the NIC was already verified as part of the troubleshooting steps performed, so repeating ipconfig provides no new diagnostic value.

Concept tested: DNS A record troubleshooting for hostname resolution

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

Topics

#DNS troubleshooting#hostname resolution#DNS A record#network connectivity

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SK0-004 Practice