Windows Still Uses an Old Address After Switching VPN? Inspect Hosts

Why old mappings may survive a route change

Microsoft documents hosts as a hostname-to-IP mapping file whose modified entries can override normal resolution. A VPN route switch may leave a local mapping in place. Treat this as a hypothesis, not a conclusion from one error.

Inspect before deciding on changes

1. Record hostname, error and time; ensure the other device tests the same URL rather than judging by appearance.
2. Open %WinDir%\System32\drivers\etc in Explorer and view hosts in Notepad without saving. A common full path is C:\Windows\System32\drivers\etc\hosts.
3. Look for an active hostname entry and note its IP and purpose. Lines starting with # and blank lines are not active mappings. Keep the full work file private.
4. Ask who added the entry and whether organizational or development networking still needs it. Compare with current official support information, not a fastest-IP list.
5. Back up before any necessary edit by an authorized maintainer following Microsoft guidance. Refer managed PCs to IT instead of clearing all mappings.
6. Retest the same URL and network. If no relevant entry exists or failure remains, investigate DNS, proxy and service status without bypassing certificate warnings.

Separate destination mapping from exit IP

Hosts inspection concerns destination lookup, not selecting a VPN exit IP. Browsers and apps can use their own resolution paths, so one result does not represent all apps. Preserve before-and-after evidence for support.