SK0-004 · Question #899
After configuring a server, a technician is unable to access websites by URL but can access websites by typing in an IP address. Which of the following is the MOST likely cause of this issue?
The correct answer is B. The DNS is misconfigured. When a user can reach websites by IP address but not by URL, the problem is with name resolution, pointing to a DNS misconfiguration.
Question
After configuring a server, a technician is unable to access websites by URL but can access websites by typing in an IP address. Which of the following is the MOST likely cause of this issue?
Options
- AThere is a misconfigured firewall.
- BThe DNS is misconfigured.
- CThe DHCP is not enabled on the server.
- DThere is an incorrect gateway configuration.
How the community answered
(39 responses)- A5% (2)
- B90% (35)
- C3% (1)
- D3% (1)
Why each option
When a user can reach websites by IP address but not by URL, the problem is with name resolution, pointing to a DNS misconfiguration.
A misconfigured firewall would block traffic by port or protocol and would prevent access by both URL and IP address, not just URL-based requests.
DNS (Domain Name System) is responsible for translating human-readable domain names into IP addresses. When DNS is misconfigured or unreachable, the system cannot resolve URLs to their corresponding IPs, but direct IP access still works because no name resolution is required. This split behavior - IP works, URL does not - is the classic symptom of a DNS failure.
DHCP not being enabled would prevent the server from obtaining an IP address automatically, which would affect all network connectivity and not only URL-based access.
An incorrect gateway would prevent routing traffic outside the local subnet, blocking external access by both URL and IP address equally.
Concept tested: DNS name resolution and network troubleshooting
Source: https://learn.microsoft.com/en-us/windows-server/networking/dns/dns-top
Topics
Community Discussion
No community discussion yet for this question.