Issue

When you run Get-NetIPInterface in PowerShell, compare the InterfaceMetric of your physical adapter (Ethernet / Wi-Fi) with the Timus adapter.

If your physical adapter's metric is lower than the Timus adapter (for example, your adapter = 1 and Timus(connect) = 5), Windows will prefer the physical adapter for routing. As a result, DNS servers behind the IPsec tunnel and/or local DNS servers may not resolve correctly. This is expected Windows behavior — the interface with the lowest metric wins.

Example

ifIndex InterfaceAlias    InterfaceMetric
------- --------------    ---------------
12      Ethernet                        1
27      connect                         5

Resolution

Reset the physical adapter to use an automatic metric so Windows can rebalance priorities:

1. Open Control Panel → Network and Internet → Network and Sharing Center.
2. Click on your active adapter (Ethernet or Wi-Fi).
3. Click Properties.
4. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
5. On the General tab, click Advanced….
6. On the IP Settings tab, check Automatic metric.
7. Click OK on all open windows.

You don’t need to disconnect or reconnect to Timus. You can check whether Timus now has a lower metric, and if it does, it should start working immediately.

Get-NetIPInterface
nslookup <internal-hostname-or-domains>

Updated June 10, 2026 12:51