I believe lan connection of the client has a higher priority/metric than the local one. That is normal. It depends on the name resolution order. Did you check the TCP/IP settings (Advanced settings) in the client? Check the metric of the gateway, DNS settings (DNS tab), and the name resolution order and there are other services too. IP/v6 also provides techniques.
Most importantly, there is a specific setting known as the VPN Binding Order. Imo, this could be the issue.
You could try the solution below. This is copied directly from this Microsoft article.
- Click Start, type regedit32 in the Open box, and then
click OK.
- Click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage
- In the right pane, double-click Bind.
- In the Value data box, select the "\Device\NdisWanIp" item, press CTRL+X, click the top of the list of devices, and then press CTRL+V.
- Click OK, and then quit Registry Editor.
- Restart the remote system.
Note: If you use an AD enabled network, you may be able to use a policy.
"Connection-specific DNS Suffix" is returned by DHCP by Option 015 Domain Name.
It tells what the domain name is, for example "contoso.com".
The client uses the information from Option 015 together with its host-name
to form the FQDN, for example PC1.contoso.com.
The computer can have a "Primary DNS Suffix" defined, which once defined
does not change.
If a different "Connection-specific DNS Suffix" is received while connecting,
it takes precedence, because this ensures that on the new network or VPN
the computer will have a proper name on the network and can find and be
found by other computers.
After disconnecting from a VPN, the "Primary DNS Suffix" will again be
the one used.
The existence or not of the "Connection-specific DNS Suffix" depends solely
on the answer returned by the DHCP server. If none is returned, then it will
stay empty and the "Primary DNS Suffix" will still be used by default.
A DHCP Option 015 name can come from the router or from the ISP,
and its presence does not depend on the network type, either wired or wireless,
but on whether DHCP returned an Option 015 name or not.
If none is received, it will stay empty.
In the post there is the assumption that a wireless network cannot have a
"Connection-specific DNS Suffix". I have searched and found several other
posts in which were published the results of ipconfig /all and in which
it was present on a wireless adapter :
link1,
link2,
link3,
and
link4.
I think that in the context of the poster, the DHCP server was probably the
wireless router, which did not return an Option 015 name.
This is determined by the wireless router's firmware rather than by other factors.
The router can maybe be programmed differently, but this is not the subject here.
Reference :
RFC 2132, DHCP Options and BOOTP Vendor Extensions, section 3.17. Domain Name.
Best Answer
Bitmap and Charles below are correct, Microsoft has added a new feature in Windows 7 called DNS Devolution, and there is a policy setting to disable it, as follows:
Run gpedit.msc Browse Local Computer Policy -> Computer Configuration -> Administrative Templates -> Network -> DNS Client
Enable "Allow DNS Suffix Appending to Unqualified Multi-Label Name Queries"
That should do it.