Examkin

Question

Difficulty: HardWindows Client Networking Configuration

A tier-2 support technician is troubleshooting network connectivity on a Windows 11 Pro client workstation. The user can ping internal servers by their IPv4 address and browse external websites using IP addresses, but cannot access internal shares using fully qualified domain names (FQDNs) like `files.corp.local`. Inspecting `ipconfig /all` reveals that the adapter has a static IP address of 192.168.1.50192.168.1.50, subnet mask 255.255.255.0255.255.255.0, default gateway 192.168.1.1192.168.1.1, and preferred DNS server 127.0.0.1127.0.0.1. Which configuration change should the technician perform to resolve the domain name resolution failure?

  1. Reconfigure the IPv4 properties of the network adapter to set the Preferred DNS server to the local domain controller IP address.Answer
  2. B
    Run ipconfig /flushdns followed by ipconfig /renew in an elevated command prompt to obtain dynamic DNS server addresses.
  3. C
    Navigate to the Network and Sharing Center applet and change the active network profile type from Public to Private.
  4. D
    Upgrade the workstation operating system edition from Windows 11 Pro to Windows 11 Enterprise to unlock client DNS resolution capabilities.

Answer

Reconfigure the IPv4 properties of the network adapter to set the Preferred DNS server to the local domain controller IP address.
The system is currently configured with the loopback address (127.0.0.1127.0.0.1) as its DNS server. Because no local DNS service is running on the workstation, domain name resolution fails. Changing the preferred DNS setting to point to the actual internal DNS server/domain controller allows the client to successfully resolve hostnames like `files.corp.local`.

Step-by-Step Solution

1
Analyze the output from ipconfig /all
Identified that the client IPv4 address, subnet mask, and gateway are configured properly on local subnet 192.168.1.0/24192.168.1.0/24, but the preferred DNS server is set to the loopback address (127.0.0.1127.0.0.1).
The loopback address directs DNS queries to the local host machine itself, which is not running a local DNS service, causing all FQDN queries to fail.
2
Determine the necessary TCP/IPv4 property modification
Specify the IP address of an active infrastructure DNS server (such as the enterprise Domain Controller).
Internal domain name resolution requires queries to be routed to a designated DNS server holding local domain zones.
3
Apply the change in Network Adapter properties
The client successfully sends DNS queries to the designated DNS server and resolves internal domain names.
Directing DNS client traffic to the correct DNS infrastructure restores full hostname-to-IP resolution.

Key Concept

Windows TCP/IP Client DNS Configuration
Estimated Time:2m 0s
Rate this question

Topics

Windows Client Networking Configuration

More questions from this topic