Several Windows 11 clients in a branch office obtain their TCP/IP settings from a Windows Server DHCP scope. After two old domain controllers (192.168.10.10 and 192.168.10.11) were replaced with new ones at the same IP addresses, users report that they can map the department share by IP (\192.168.10.25\Dept) but receive The network resource is unavailable when they try the hostname (\FS1.contoso.local\Dept). You verify that the A record for FS1.contoso.local points to 192.168.10.25.
On one affected workstation you run ipconfig /all and note:
Name resolution is failing because the workstations are sending queries to the wrong DNS servers (192.168.50.10 and 192.168.50.11). The quickest way to correct this for every client is to fix the DHCP scope so option 006 hands out the correct DNS server addresses for the site (192.168.10.10 and 192.168.10.11) and then have clients renew their leases. Clearing caches or disabling IPv6 would not help while the incorrect DNS servers are still in use. SMB signing and record TTL do not affect whether a hostname can be resolved.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is DHCP scope option 006 and what does it do?
Open an interactive chat with Bash
Why is renewing a DHCP lease necessary after updating the DHCP scope?
Open an interactive chat with Bash
Why wouldn't clearing caches or disabling IPv6 resolve this issue?
Open an interactive chat with Bash
What does DHCP scope option 006 do?
Open an interactive chat with Bash
Why is DNS important in name resolution?
Open an interactive chat with Bash
What is the function of `ipconfig /release` and `ipconfig /renew`?
Open an interactive chat with Bash
What is DHCP scope option 006 and why is it important?
Open an interactive chat with Bash
Why is releasing and renewing DHCP leases necessary after updating the scope?
Open an interactive chat with Bash
Why do the incorrect DNS servers (192.168.50.10 and 192.168.50.11) cause name resolution failure?