Protect Yourself From Tech Support Scams
Learn More
October 14, 2019
Protect Yourself From Tech Support Scams
Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee
and that the phone number is an official Microsoft global customer service number.
Exact same works for me. SplitTunneling was always off and that's what I want as I need to resolve remote addresses, but it was defaulting to my LAN gateway.
Disabled IPv6 and sure enough, remote resolves now.
This is a definite bug introduced in Windows 10. My connections are exactly as they were configured in 8.1 where they worked fine.
2 people were helped by this reply
·
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
I believe the problem you are seeing is stemming from the fact that in Windows 8.1 the DNS Client began sending IPv4 & IPv6 queries in parallel. Where as in previous OS's the IPv4 query was sent and then the IPv6 query was serialized.
So what I believe is happening is that the IPv6 query is hitting your ISP first and responding in such a way as to make the DNS Client think the name is unresolvable.
Other replies to this thread support this since they indicate that disabling IPv6 makes the name resolution work the way you need it too. So another way to fix this would be to revert the DNS Client behavior to be like it used to be, you can accomplish that
by setting this registry key:
I believe the problem you are seeing is stemming from the fact that in Windows 8.1 the DNS Client began sending IPv4 & IPv6 queries in parallel. Where as in previous OS's the IPv4 query was sent and then the IPv6 query was serialized.
It was also working on Win 7 and 8 and 8.1 ... so if only Win 8.1 hat this feature it is not the real problem.
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
Ok, since this seems to be a split tunnel issue. Do you notice any difference when using fully qualified domain names as opposed to short names? Also take a look at ipconfig /all and see if the VPN interface has DNS suffixes configured for it that correspond
to the domain names reachable only over the VPN. Lastly, have you taken a look at the routing metrics for the VPN interface vs your LAN\ISP? The DNS client uses this to determine the interface to use if the interfaces are missing any suffix configuration.
1 person was helped by this reply
·
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
FQDN's also don't work when either split tunneling or IPv6 is enabled. It doesn't use my companies DNS server for any query in that case (it does without split tunneling and IPv6 disabled).
Here is the command line output of (ipconfig /all, route print and nslookup). I use a static IP adres on my PC. I also tried with DHCP, but it didn't make a difference.