<div>
At the TCP/IP Promerties, in the Network Connection that is configured to receive the VPN connections, uncheck the &quot;Register this connection addresses in DNS&quot; option, and see if it corrects the problem.
</div>


At the TCP/IP Promerties, in the Network Connection that is configured to receive the VPN connections, uncheck the "Register this connection addresses in DNS" option, and see if it corrects the problem.

<div>
I found the solution myself
</div>


<div>
<div class="content wysiwyg-content">
I have configured VPN on a Windows 2008 Server with IP address of 10.0.0.x. &nbsp;The clients can connect and access data remotely, but when a client connects on IP 10.0.0.y, a DNS A record is created in the DNS. &nbsp;The client then disconnects and the A record remains in DNS. &nbsp;A local user then tries to access a mapped drive on the server, but the servername is resolving to 10.0.0.y which is the disconnect VPN IP, where as it should be resolving to 10.0.0.x which is the servers LAN IP. &nbsp;How can I stop this A record going in to the DNS table?
</div>
</div>


I have configured VPN on a Windows 2008 Server with IP address of 10.0.0.x.  The clients can connect and access data remotely, but when a client connects on IP 10.0.0.y, a DNS A record is created in the DNS.  The client then disconnects and the A record remains in DNS.  A local user then tries to access a mapped drive on the server, but the servername is resolving to 10.0.0.y which is the disconnect VPN IP, where as it should be resolving to 10.0.0.x which is the servers LAN IP.  How can I stop this A record going in to the DNS table?

Server 2008 VPN creates DNS A record for VPN IP

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.