Several Windows Server 2022 file servers on VLAN 30 are reachable by IPv4 address but cannot be reached by their hostnames. From an affected client you run the following commands:
C:\> ping 10.30.0.12
Reply from 10.30.0.12: bytes=32 time<1ms TTL=128
C:\> nslookup filesrv01 10.30.0.12
*** Request to 10.30.0.12 timed-out
The IP address 10.30.0.12 belongs to a domain controller that also runs DHCP and DNS. Clients are still receiving valid DHCP leases, and no recent network-infrastructure changes were made.
Which action will MOST likely restore normal name resolution with the least disruption?
Increase the DHCP lease duration on the scope that serves VLAN 30
Flush the DNS client cache on every workstation
Start or restart the DNS Server service on 10.30.0.12
Clear the ARP table on the layer-3 switch that routes VLAN 30
The client can reach the server's IP address, so routing, VLANs, and cabling are functioning. However, nslookup times out when it contacts the same host on UDP/TCP port 53, indicating that the DNS Server service on 10.30.0.12 is not responding even though the host is online. Microsoft troubleshooting guidance states that a "Request to server timed out" response usually means the DNS service is stopped and should be restarted. Restarting (or starting) the DNS Server service will bring port 53 back online and immediately allow clients to resolve hostnames again.
Flushing the DNS cache on every client would not help, because the server is not answering queries. Changing the DHCP lease duration does not affect DNS resolution, and clearing the ARP table on the switch is irrelevant because layer-2 reachability is already verified by the successful ping.