mapped drives in Win 10 not working with VPN on remote computers

Windows server 2008 R2 Domain Controller

Windows 10 x64 desktop (fresh install updated as of 10-14-2015)
Offline files have been setup
Users documents folder is mapped to \\server02\userdata$\user
Mapped network drives show up and can be accessed

I have setup offline files on this desktop because I want it to work just like a laptop that is off the network would work. When a user with a laptop connects to the office through the VPN any changes they have made to documents will sync with their user folder on the server. It also allows them access to other mapped network drives (Public, Accounting, Projects, etc.).

So this is how it currently works with a windows 7 pro setup

1)      login to the computer while it is connected to the domain.
2)      open the Public network drive
3)      shut down the computer
4)      go home, login to your computer, connect to your network.
5)      I get the usual error about not all network drives connected, but all the mapped drives are still there but now they have red X’s on them to denote the connection to that drive is not up. So if you try to open the Public drive it gives you an error to let know that you can’t access it. (this is expected behavior)
6)      the drive that is mapped to \\server02\userdata$\user is still there and shows up as Network Drive (H:) and I can access the offline versions of the files just cant get to the network version of the files.
7)      Start up the vpn connection to the server
8)      Open the public drive and you have access to the files

So why does this not work the same with windows 10?

If I follow the same procedure as above with a windows 10 setup, I get the usual error message about not all network drives connected which is what is supposed to do.

I start up the VPN and try to access the Public drive and it says its not there.
the network drives are visible with the red X’s on them, and should open as they do in step 8 on the Windows 7 setup but they don’t.

To top it all off, I rebooted the computer and the network drives are now all gone, no message about not all network drives were reconnected, no drives with red X’s on them, just nothing.

So I think maybe a DNS issue (still think the is the problem but need some help so here I am)

So with the VPN up I try to ping the server by name and not IP address

ping server01
Pinging server01.domain.local [192.168.1.30] with 32 bytes of data
Reply from 192.168.1.30: bytes=32 time=58ms TTL=127
Reply from 192.168.1.30: bytes=32 time=58ms TTL=127
Reply from 192.168.1.30: bytes=32 time=58ms TTL=127
Reply from 192.168.1.30: bytes=32 time=58ms TTL=127

So this ping works exactly as it should

I try to ping another server on the network and this is what happens

ping server02
Pinging server02.Home [198.105.244.23]-- where the heck does .home come from and why?
Request timed out.
Request timed out.
Request timed out.
Request timed out.

nslookup domain.local
server: domain.local
address: 198.105.254.23 <-----????? should be 192.168.1.31

DNS request timed out.
      Timeout was 2 seconds

http://www.networksolutions.com/whois/results.jsp?ip=198.105.244.23

I can ping all four servers at the other end of the VPN rainbow by IP address just fine.

sorry bout the long post, sometimes more info is helpful, I hope this is one of those times.

Any help would be appreciated

V