Windows cannot resolve custom domains when VPN is up?

Posted on

QUESTION :

We have a DNS server on local network which has some custom TLDs such as “local, dummy” etc. The domains ending with these TLDs resolves to test servers like win2003test.dummy.

The problem occures when a VPN connection is up. Windows tries to resolve these domain with another DNS server assigned by VPN server. This prevents dummy domain-to-ip translations.

Is there an easy setting somewhere with which I can overcome this issue?

PS: Remote gateway in VPN setting is disabled.

ANSWER :

I assume that you are talking about when clients VPN into the network?

I see a few solutions, all of which are pretty easy.

  1. Setup the VPN to issue a DNS server which has the .dummy TLD in it.
  2. Setup the DNS server which the VPN issues to have stub records which point to the correct internal DNS servers for the .dummy TLD.
  3. Setup the DNS server which the VPN issues to be a secondary DNS server for the .dummy TLD.

It seems to me that what you’re asking is how to configure a split DNS.

See if this article helps:
Configure a split DNS system on Windows Server 2003

In a lesser way, see also:
In a multi-DNS server environment, how do I configure the DNS servers to resolve both local and remote hosts?

You could enter them in the computer’s C:WindowsSystem32driversetchosts file. Trying to modify the DNS server you’re pointed to will only cause problems resolving hosts on the other side of the VPN.

Sorry, not an answer to your question, but just to be sure you know what you’re doing:

We have a DNS server on local network

…and:

The problem occures when a VPN connection is up.

I wonder about the “a” in “a VPN connection”: is this a VPN connection to some third-party server?

If yes, then:

Remote gateway in VPN setting is disabled.

So, you actually want your local network (and its local test servers) and that third-party VPN to be interconnected?

Leave a Reply

Your email address will not be published. Required fields are marked *