Running Windows 10 Pro Build 10240.

Created an L2TP/IPSec VPN connection to work.

The properties button on IPV4 for this connection does not work.  You can click it all day and nothing happens.

Basically, I'm trying to set the DNS Suffix for this connection, e.g. mywork.com so that when I ping PC1, it pings PC1.mywork.com

Working around this I manually edited the rasphone.pbk and changed the IpDnsSuffix=mywork.com

Even after all this, Windows 10 seems to be ignoring the suffix.  

Ping pc1.mywork.com works perfectly

ping pc1 on its own, and dns does not resolve it.

I was going to report this via Windows Feedback, but that doesn't seem to work for me either.  It wants a setting changed that I cannot change as it's "Managed by the Insider Program" or something like that.

Anyone else come across this?

Basically, I'm trying to set the DNS Suffix for this connection, e.g. mywork.com so that when I ping PC1, it pings PC1.mywork.com

Does a HOSTS override work?  It might affect how a host sees your requests, e.g. for HTTP, but it wouldn't matter for ICMP (e.g. ping).

BTW any clues from the PowerShell command  Get-NetConnectionProfile

I'm wondering if this is an IPv6 versus IPv4 thing, especially because of the mention of IPSec.  So, related to that, can you put that connection in the Homegroup?

Good luck

HOSTS override does work perfectly, but I can't go adding all my machines into that :)

Get-NetConnectionProfile shows nothing unusual.

I even disabled IPv6 on that VPN connection, but it makes no difference.

It's almost like Win10 is ignoring the DNS suffix I have set it.

Exactly the same setup on Win 8.1 works perfectly.

Win 8.1 ---> PING PC1 and it responds, therefore suffix being appended.

Win 10 ---> PING PC1 and it dies, therefore suffix NOT being appended.

It's almost like Win10 is ignoring the DNS suffix I have set it.

But that was set more hopefully than systematically?

Try some more PowerShell workarounds.  E.g. this has a -DNSSuffix switch. 

Set-VpnConnectionTriggerDnsConfiguration

and the Synopsis of Add-VpnConnectionTriggerTrustedNetwork at least sounds promising.

PS>(Get-Help Add-VpnConnectionTriggerTrustedNetwork).Synopsis
Adds DNS suffixes as trusted networks to the VPN profile.

No Synopsis seen on the Set- command is why I jumped to that one.

PS>Get-Help *vpn*trig* | ft Name, Synopsis -AutoSize

Otherwise sketchy documentation IMO.  E.g. the Get-VpnConnectionTrigger cmdlet which presumably would be related has zero clues in its help about how.

Is it any more closely related to what you were trying to do but weren't allowed to?  Notice also that there is a -Force switch available.  Maybe you will at least get some clues about the implementation from this approach.

WTH is a "trigger" anyway?  Sounds like some kind of user exit analog for third-party VPN products?  Does your VPN provider document any of this?

Also supposedly there are some relevant trace events you could try looking for

http://blogs.technet.com/b/networking/archive/2013/10/03/automatically-triggering-vpn-connections-and-vpn-diagnostics-enhancements-in-windows-8-1.aspx 

<quote>

Windows Networking Vpn Plugin Platform/Operational and Microsoft-Windows-VPN/Operational.
</quote>

Good luck

Hi alanplum,

Thanks for reporting, I tested on my machine and same result with you. You could use the build in feedback tool to report this issue to us. The VPN feature has been completely improved in Windows 10, the official article will be released soon after 29 July. Regarding to this issue, Your reply will be marked as an answer. Thanks for your understanding.

Regards,

D. Wu

Hi alanplum,

Thanks for reporting, I tested on my machine and same result with you. You could use the build in feedback tool to report this issue to us. The VPN feature has been completely improved in Windows 10, the official article will be released soon after 29 July. Regarding to this issue, Your reply will be marked as an answer. Thanks for your understanding.

Regards,