D
D_Goossens
Hi,
We're performing an Always On VPN project, and have an issue with DNS resolution.
In general we want the AOVPN interface to have a lower metric then the wired NIC.
THe DNS gets chosen, based on the interface with the lowest metric.
We're using a script from Richard Hicks to change the metric of the AOVPN interface.
(richardhicks/aovpn)
It does get set correctly, and is being changed in the rasphone.pbk file located in : "C:\ProgramData\Microsoft\Network\Connections\"
(we're installing it for all users, hence the location of the file).
So far, so good.. Everything seems to get adapted correctly (verified metric on GUI interface too, and it shows the changed metric).
However when a client connects via VPN, they still get the ISP DNS server (via wired interface) to respond instead of the internal DNS server.
Lowering the metric of the AOVPN interface, should have forced this DNS to be used.
Now for the question
When checking the metric of the connections via "netsh interface ipv4 show interfaces", the metric is correct (we see the changed one)
When checking via Get-NetIPInterface, the old value is still shown, valued 25, which is automatic. This is the metric being used, and the one queried with netsh is being ignored.
DOes anyone know why there is a difference in both ways to query them?
Continue reading...
We're performing an Always On VPN project, and have an issue with DNS resolution.
In general we want the AOVPN interface to have a lower metric then the wired NIC.
THe DNS gets chosen, based on the interface with the lowest metric.
We're using a script from Richard Hicks to change the metric of the AOVPN interface.
(richardhicks/aovpn)
It does get set correctly, and is being changed in the rasphone.pbk file located in : "C:\ProgramData\Microsoft\Network\Connections\"
(we're installing it for all users, hence the location of the file).
So far, so good.. Everything seems to get adapted correctly (verified metric on GUI interface too, and it shows the changed metric).
However when a client connects via VPN, they still get the ISP DNS server (via wired interface) to respond instead of the internal DNS server.
Lowering the metric of the AOVPN interface, should have forced this DNS to be used.
Now for the question
When checking the metric of the connections via "netsh interface ipv4 show interfaces", the metric is correct (we see the changed one)
When checking via Get-NetIPInterface, the old value is still shown, valued 25, which is automatic. This is the metric being used, and the one queried with netsh is being ignored.
DOes anyone know why there is a difference in both ways to query them?
Continue reading...