A user on a Windows client workstation reports being unable to connect to an internal web application at `intranet.corp.local` after the server was migrated to a new IP address (`192.168.1.50`). A technician executes `ipconfig /displaydns` on the client workstation and receives the following output:
text
Record Name . . . . . : intranet.corp.local
Record Type . . . . . : 1
Time To Live . . . . : 86400
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 192.168.1.250
Which TWO of the following actions or events will resolve this name resolution issue on the client workstation? (Select TWO.)
- Run the `ipconfig /flushdns` command on the client workstation.Answer
- Wait for the 86400-second Time To Live (TTL) period of the cached entry to expire.Answer
- CRun the `ipconfig /registerdns` command on the client workstation.
- DReconfigure the client resolver to send DNS queries over TCP port 53 instead of UDP port 53.
Answer
The issue is resolved by running `ipconfig /flushdns` to immediately purge the stale cached record, or by allowing the entry's Time To Live (TTL) duration to naturally expire.
The client workstation is resolving the hostname to an outdated IP address because the entry is saved in the local OS DNS resolver cache. Executing the command to flush the DNS cache immediately purges all cached entries, forcing the workstation to perform a fresh DNS query against the server. Alternatively, allowing the Time To Live (TTL) timer of 86,400 seconds to naturally expire will cause the operating system to automatically remove the stale entry from memory.
Step-by-Step Solution
Key Concept
Stale DNS Resolver Cache and TTL Management