A Windows 11 client workstation in an enterprise environment can successfully access internet websites by URL and reach local resources using IP addresses. However, when users attempt to connect to internal file servers using domain hostnames (such as \\fileserver.corp.local), the connection fails. A technician runs `ipconfig /all` and observes that the IPv4 network adapter is configured with a static IP of 10.1.5.50, a gateway of 10.1.5.1, and public DNS servers (8.8.8.8 and 8.8.4.4). Which of the following networking updates will resolve the hostname resolution failure while maintaining internet connectivity?
- Reconfigure the primary DNS server IP address to point to the internal Active Directory domain controller.Answer
- BAdd a secondary default gateway address corresponding to the local domain controller's IP address.
- CRun the command `ipconfig /flushdns` with the switch `/release` to clear invalid gateway routes.
- DOpen Network Connections in Control Panel and enable the Windows Feature switch for Active Directory Name Resolution.
Answer
Reconfigure the primary DNS server IP address on the network adapter to point to the internal Active Directory domain controller.
Internal active directory domain names can only be resolved by internal DNS servers containing the local zone files. Assigning public DNS servers prevents clients from locating internal network shares by hostname.
Step-by-Step Solution
Key Concept
Windows TCP/IP Client DNS Configuration for Internal Domain Name Resolution