## TL;DR
Split DNS on Windows 11 breaks when the VPN adapter is not the one answering internal queries: wrong adapter DNS order, missing Name Resolution Policy Table rules, or the VPN client not pushing them. Check which adapter answers the query first, then fix the NRPT or adapter settings.

## The query
```text
vpn split dns not working on windows 11
```

## Use this when
- internal hostnames do not resolve while the VPN is connected
- nslookup gives the public answer for an internal name
- split DNS worked on Windows 10 but broke on 11

## Not for
- full-tunnel VPNs where all DNS goes through the tunnel
- DNS working but traffic not routing (different problem)
- the VPN client not connecting at all

## Steps
1. With the VPN connected, run nslookup for an internal hostname and note which server answers. Expected output: you see which DNS server handled the query
2. Check the VPN adapter's DNS servers in the adapter settings. Expected output: the corporate DNS servers listed on the VPN adapter
3. Check the Name Resolution Policy Table with Get-DnsClientNrptPolicy for rules covering the internal domain. Expected output: NRPT rules present or confirmed missing
4. If rules are missing, check the VPN client or profile settings that should push them. Expected output: the source of the missing rules identified
5. Confirm no third-party DNS or VPN-adjacent software is overriding resolution. Expected output: no conflicting resolver
6. Reconnect the VPN and retest the internal hostname. Expected output: the internal name resolves to the internal address

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_thJuYoBNa4Kji1U7h_LdRQ