Hello. I am new to this forum so please accept my apologies if I do something incorrectly.

I have a Windows VPN configured on a Server 2008 R2 machine. When I connect from a remote workstation I get a third DNS entry that is listed above the expected DNS addresses. The DNS address shown is Can anyone help me figure out why this is happening and how to resolve it? Currently I need to run the command below to remove the unwanted DNS entry.

netsh interface ipv4 delete dnsservers name="name of the VPN" address=all validate=no

Thank you,

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In routing and remote access, you have selected to use the VPN server as the gateway to the internet.  Check your settings there.   I don't have access to a Routing and remote access server to walk you thru the steps, sorry.
Mike_K123Author Commented:
Thank you for the comment, ktaczala. In the VPNServer properties I have the "Enable this computer" section set to use "LAN and demand dial routing". Changing this setting to "Local Area network routing only" does not help. I hope this is the setting you were pointing out but unfortunately this did not fix the problem.
Mike_K123Author Commented:
I was able to trace this back to DHCP.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mike_K123Author Commented:
This was a setting in DHCP. We have two servers sharing the role of DHCP. Settings were reviewed on one server but not the other. One of the servers listed the DNS address as a valid address. Once removed our issue was gone.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.