A network administrator is configuring and troubleshooting Windows client network interfaces in an enterprise environment. Match each specific administrative objective on the left with the exact command-line tool syntax or Advanced TCP/IP configuration setting on the right.
- Statically assign a primary IPv4 DNS server address of 192.168.1.10 to an interface named 'Ethernet0' using the command line.netsh interface ipv4 set dns name="Ethernet0" static 192.168.1.10
- Query an internal DNS server directly to verify the Start of Authority (SOA) resource record for the corporate domain.nslookup -type=SOA corp.internal
- Prevent the Windows client from automatically registering its IP address and primary domain suffix in DNS for a specific NIC.Clear the 'Register this connection's addresses in DNS' checkbox in Advanced TCP/IP DNS Settings.
- Reset the Windows Sockets and IP stack registry keys to default configurations to clear severe network driver corruption.netsh int ip reset c:\resetlog.txt
Answer
The correct pairings match each administrative networking scenario with its precise Windows CLI command or TCP/IP configuration setting: static DNS assignment uses netsh interface ipv4 set dns; DNS zone SOA verification uses nslookup -type=SOA; disabling automatic dynamic DNS updates uses the Advanced TCP/IP DNS property setting; and complete TCP/IP protocol stack restoration uses netsh int ip reset.
Each administrative requirement corresponds directly to a specific Windows network management tool or setting. Static command-line DNS assignment requires 'netsh interface ipv4 set dns'. Specific DNS record lookups require 'nslookup' with record type parameters like '-type=SOA'. Dynamic DNS registration controls are managed via the Advanced TCP/IP DNS property tab. Core protocol stack corruption recovery is performed using 'netsh int ip reset'.
Step-by-Step Solution
Key Concept
Windows Client Network Adapter Configuration and Diagnostic CLI Commands