DNS Resolver Uses Local DNS Server rather than VPN Provided DNS Servers

[GeekMarine1972]

Platform: Windows XP SP2
Configuration: Local network connection + MS VPN connection to remote
location (i.e. PPTP or L2TP using MS client / server).


Issue Summary:

Ipconfig shows 2 interfaces, local ethernet and vpn pptp. Both show an
ip address considered local, both list DNS servers. First interface
lists IP address of 192.168.200.2, default gateway 192.168.200.1, DNS
server 192.168.200.1. It is connected to a home firewall / router that
proxies DNS requests (typical for most home use firewall / routers.
Abnoxiously, the DNS server on the firewall does not provide
configuration of DNS servers). So yes, the firewall is one source of
annoyance but not entirely. Second interface PPP adapter with Ip
address of 10.0.0.33, gateway 10.0.0.33 (typical for VPN client), and
lists 2 DNS servers 10.0.0.2 and 10.10.0.3.

The problem arises when a users enters ANY url into or run NSLookup,
the first DNS server query is those tied to the local interface, not
the VPN. If the local adapter's DNS servers are not on the local
network, requests are still sent to it, but in many cases time out or
fail, and requests are then sent to the DNS servers tied to the VPN
adapter.

This causes issues with split DNS. If the local adapter's DNS queries
are sent to the firewall which proxies and send back a response, the
result of the DNS query is the public IP address for a resource, when
the expectation is that DNS queries will go to the VPN DNS server first
and return the private IP address. Because local adapter DNS is
queried first, things like shortname resolution to access file shares
fails.

This appears to have broken in SP2 of Windows XP, with RASPPP.DLL
5.1.2600.2180 dated Tuesday, August 03, 2004, 11:56:44 PM.

Is there a registry hack to modify the resolver order. My current work
around is to assign a non local DNS server manually to the local
adapter and then set the timeout for dns cache and dns resolution down
to 1 second. Seems to function but not really an attractive solution.

The obvious preference would be that the PPP adapter be treated as
local and it's DNS entries treated as preferential.

If it makes any difference, the local adapter is wireless, but I am
fairly certain it behaves the same way on wired adapters.

Paul V.

 

[guyton3]

Anyone found a solution for this? This has been an issue of mine for quite a while now, too.

Thanks,
Bill

 

[Robert L [MS-MVP]]

assuming you have windows RRAS as VPN server, the VPN client takes the server DNS. you may assign another DNS manually.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Anyone found a solution for this? This has been an issue of mine for
quite a while now, too.

Thanks,
Bill

 

[Guest]

I too am having this problem.

I have DNS names that I need to resolve to one IP address internally or when
VPNed, and a different IP address externally. However, when VPNed, the VPN
client is resolving the DNS name to the external IP address.

The VPN client does receive the DNS server from the VPN server, but uses the
local DNS server instead.

If I manually enter in the VPN server's DNS entry as the local DNS entry,
then it starts resolving the correct internal IPs for the VPN client, but
there has to be a more appropriate solution than asking the VPN client to
manually enter in DNS entries on his or her computer.

 

[Robert L [MS-MVP]]

posting the result of ipconfig /all may help. Also assuming the remote LAN DHCP will assign IP, DNS to the VPN client.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
I too am having this problem.

I have DNS names that I need to resolve to one IP address internally or when
VPNed, and a different IP address externally. However, when VPNed, the VPN
client is resolving the DNS name to the external IP address.

The VPN client does receive the DNS server from the VPN server, but uses the
local DNS server instead.

If I manually enter in the VPN server's DNS entry as the local DNS entry,
then it starts resolving the correct internal IPs for the VPN client, but
there has to be a more appropriate solution than asking the VPN client to
manually enter in DNS entries on his or her computer.

 

[Guest]

Here is the result of an ipconfig /all. Out of paranoia, I've changed some
of the info, but you should get the gist of the problem:
----------------------------------------------------
C:\Documents and Settings\JWM>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : JWMlaptop
Primary Dns Suffix . . . . . . . : mycompany.corp
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mycompany.corp
se1.client2.attbi.com
mycompany-corp

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : se1.client2.attbi.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG
Network Connection
Physical Address. . . . . . . . . : 00-13-CE-29-AD-D7
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, September 08, 2005
12:18:21 AM
Lease Expires . . . . . . . . . . : Sunday, September 11, 2005
12:18:21 AM

PPP adapter VPNServer:

Connection-specific DNS Suffix . : mycompany-corp
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.4.10.10
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.4.10.10
DNS Servers . . . . . . . . . . . : 10.4.2.15

C:\Documents and Settings\JWM>nslookup
*** Can't find server name for address 192.168.0.1: Non-existent domain
Default Server: officeDNSserver.mycompany.corp
Address: 10.4.2.15

exit

C:\Documents and Settings\JWM>ping -a 10.4.2.66

Pinging www.JWM.com [10.4.2.66] with 32 bytes of data:

Reply from 10.4.2.66: bytes=32 time=80ms TTL=126
Reply from 10.4.2.66: bytes=32 time=366ms TTL=126
Reply from 10.4.2.66: bytes=32 time=368ms TTL=126
Reply from 10.4.2.66: bytes=32 time=388ms TTL=126

Ping statistics for 10.4.2.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 388ms, Average = 300ms

C:\Documents and Settings\JWM>ping www.JWM.com

Pinging www.JWM.com [207.158.206.145] with 32 bytes of data:

Reply from 207.158.206.145: bytes=32 time=83ms TTL=63
Reply from 207.158.206.145: bytes=32 time=373ms TTL=63
Reply from 207.158.206.145: bytes=32 time=343ms TTL=63
Reply from 207.158.206.145: bytes=32 time=375ms TTL=63

Ping statistics for 207.158.206.145:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 375ms, Average = 293ms
----------------------------------------
I want to be using the DNS from the PPP adapter's DNS entry. An NSLookup
confirms that 10.4.2.15 is the DNS server I should be using. However, I am
not. I appear to still be using the local DNS first.

I can ping the internal IP address (10.4.2.66), and it even resolves the DNS
name when I do a ping -a to the internal IP address. However, when I ping
the DNS name it resolves to the public/external IP address.

Everything in this setup is Microsoft - the internal DNS & DHCP server is
one Windows server, the RAS - VPN server is another windows server, the VPN
client is a Windows machine. The remote LAN in this instance is a wireless
router that assigns the local IP and DNS. I can only get DNS names to
properly resolve to the internal IP address under two scenarios:

1. If the local DNS is screwed up and doesn't work, then the VPN client will
use the DNS from 10.4.2.15
2. If you manually put in 10.4.2.15 as your local primary DNS on the VPN
client (and, if you like, the actual local DNS as your SDNS)

 

[Guest]

I agree and also suffer from your same situation. I believe the issue
resides in how Microsoft handles traffic that should be sent through the VPN
tunnel. Under the IP properties of the VPN connection and clicking Advanced,
it will bring up the Advanced TCP/IP Settings which on the General Tab a
check box says "Use default gateway on remote network"

However, in the description of this check box, it states "data that cannot
be sent on the local network is forwarded to the dial-up network". This
being said, the DNS server used to connect to the Internet PRIOR to the VPN
connection is LOCAL. According to the description, your workstation will
send the DNS query to the local DNS server (192.168.0.1).

I think this is a security flaw that should be addressed by Microsoft as it
is a form of split tunneling. This setting implies that I can still
communicate with devices on my home network (local) while having a VPN
connection established. This potentially allows someone on the internal
network hijack my workstation while I am connected to the VPN. This is in my
mind NOT disabling split tunneling.

Cisco's VPN client implementation does enforce no split tunneling by
forwarding ALL packets through the tunnel including any packet that would
normally be destined for a local network. This can confuse end users because
when connected to the VPN, they cannot even see anything on their home
network. However, this is truely disabling split tunneling and should be the
way it works.

I am supprised the Microsoft client would allow this and I suspect that
there may be a registry setting to forward ALL packets through an established
tunnel but I have been unsuccessful at finding it. Any help or valid
workaround would be greatly appreciated.

Here is the result of an ipconfig /all. Out of paranoia, I've changed some
of the info, but you should get the gist of the problem:
----------------------------------------------------
C:\Documents and Settings\JWM>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : JWMlaptop
Primary Dns Suffix . . . . . . . : mycompany.corp
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mycompany.corp
se1.client2.attbi.com
mycompany-corp

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : se1.client2.attbi.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG
Network Connection
Physical Address. . . . . . . . . : 00-13-CE-29-AD-D7
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, September 08, 2005
12:18:21 AM
Lease Expires . . . . . . . . . . : Sunday, September 11, 2005
12:18:21 AM

PPP adapter VPNServer:

Connection-specific DNS Suffix . : mycompany-corp
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.4.10.10
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.4.10.10
DNS Servers . . . . . . . . . . . : 10.4.2.15

C:\Documents and Settings\JWM>nslookup
*** Can't find server name for address 192.168.0.1: Non-existent domain
Default Server: officeDNSserver.mycompany.corp
Address: 10.4.2.15

exit

C:\Documents and Settings\JWM>ping -a 10.4.2.66

Pinging www.JWM.com [10.4.2.66] with 32 bytes of data:

Reply from 10.4.2.66: bytes=32 time=80ms TTL=126
Reply from 10.4.2.66: bytes=32 time=366ms TTL=126
Reply from 10.4.2.66: bytes=32 time=368ms TTL=126
Reply from 10.4.2.66: bytes=32 time=388ms TTL=126

Ping statistics for 10.4.2.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 388ms, Average = 300ms

C:\Documents and Settings\JWM>ping www.JWM.com

Pinging www.JWM.com [207.158.206.145] with 32 bytes of data:

Reply from 207.158.206.145: bytes=32 time=83ms TTL=63
Reply from 207.158.206.145: bytes=32 time=373ms TTL=63
Reply from 207.158.206.145: bytes=32 time=343ms TTL=63
Reply from 207.158.206.145: bytes=32 time=375ms TTL=63

Ping statistics for 207.158.206.145:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 375ms, Average = 293ms
----------------------------------------
I want to be using the DNS from the PPP adapter's DNS entry. An NSLookup
confirms that 10.4.2.15 is the DNS server I should be using. However, I am
not. I appear to still be using the local DNS first.

I can ping the internal IP address (10.4.2.66), and it even resolves the DNS
name when I do a ping -a to the internal IP address. However, when I ping
the DNS name it resolves to the public/external IP address.

Everything in this setup is Microsoft - the internal DNS & DHCP server is
one Windows server, the RAS - VPN server is another windows server, the VPN
client is a Windows machine. The remote LAN in this instance is a wireless
router that assigns the local IP and DNS. I can only get DNS names to
properly resolve to the internal IP address under two scenarios:

1. If the local DNS is screwed up and doesn't work, then the VPN client will
use the DNS from 10.4.2.15
2. If you manually put in 10.4.2.15 as your local primary DNS on the VPN
client (and, if you like, the actual local DNS as your SDNS)

posting the result of ipconfig /all may help. Also assuming the remote LAN DHCP will assign IP, DNS to the VPN client.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
I too am having this problem.

I have DNS names that I need to resolve to one IP address internally or when
VPNed, and a different IP address externally. However, when VPNed, the VPN
client is resolving the DNS name to the external IP address.

The VPN client does receive the DNS server from the VPN server, but uses the
local DNS server instead.

If I manually enter in the VPN server's DNS entry as the local DNS entry,
then it starts resolving the correct internal IPs for the VPN client, but
there has to be a more appropriate solution than asking the VPN client to
manually enter in DNS entries on his or her computer.

 

[Guest]

I agree and also suffer from your same situation. I believe the issue
resides in how Microsoft handles traffic that should be sent through the VPN
tunnel. Under the IP properties of the VPN connection and clicking Advanced,
it will bring up the Advanced TCP/IP Settings which on the General Tab a
check box says "Use default gateway on remote network"

However, in the description of this check box, it states "data that cannot
be sent on the local network is forwarded to the dial-up network". This
being said, the DNS server used to connect to the Internet PRIOR to the VPN
connection is LOCAL. According to the description, your workstation will
send the DNS query to the local DNS server (192.168.0.1).

I think this is a security flaw that should be addressed by Microsoft as it
is a form of split tunneling. This setting implies that I can still
communicate with devices on my home network (local) while having a VPN
connection established. This potentially allows someone on the internal
network hijack my workstation while I am connected to the VPN. This is in my
mind NOT disabling split tunneling.

Cisco's VPN client implementation does enforce no split tunneling by
forwarding ALL packets through the tunnel including any packet that would
normally be destined for a local network. This can confuse end users because
when connected to the VPN, they cannot even see anything on their home
network. However, this is truely disabling split tunneling and should be the
way it works.

I am supprised the Microsoft client would allow this and I suspect that
there may be a registry setting to forward ALL packets through an established
tunnel but I have been unsuccessful at finding it. Any help or valid
workaround would be greatly appreciated.

Here is the result of an ipconfig /all. Out of paranoia, I've changed some
of the info, but you should get the gist of the problem:
----------------------------------------------------
C:\Documents and Settings\JWM>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : JWMlaptop
Primary Dns Suffix . . . . . . . : mycompany.corp
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mycompany.corp
se1.client2.attbi.com
mycompany-corp

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : se1.client2.attbi.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG
Network Connection
Physical Address. . . . . . . . . : 00-13-CE-29-AD-D7
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, September 08, 2005
12:18:21 AM
Lease Expires . . . . . . . . . . : Sunday, September 11, 2005
12:18:21 AM

PPP adapter VPNServer:

Connection-specific DNS Suffix . : mycompany-corp
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.4.10.10
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.4.10.10
DNS Servers . . . . . . . . . . . : 10.4.2.15

C:\Documents and Settings\JWM>nslookup
*** Can't find server name for address 192.168.0.1: Non-existent domain
Default Server: officeDNSserver.mycompany.corp
Address: 10.4.2.15

exit

C:\Documents and Settings\JWM>ping -a 10.4.2.66

Pinging www.JWM.com [10.4.2.66] with 32 bytes of data:

Reply from 10.4.2.66: bytes=32 time=80ms TTL=126
Reply from 10.4.2.66: bytes=32 time=366ms TTL=126
Reply from 10.4.2.66: bytes=32 time=368ms TTL=126
Reply from 10.4.2.66: bytes=32 time=388ms TTL=126

Ping statistics for 10.4.2.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 388ms, Average = 300ms

C:\Documents and Settings\JWM>ping www.JWM.com

Pinging www.JWM.com [207.158.206.145] with 32 bytes of data:

Reply from 207.158.206.145: bytes=32 time=83ms TTL=63
Reply from 207.158.206.145: bytes=32 time=373ms TTL=63
Reply from 207.158.206.145: bytes=32 time=343ms TTL=63
Reply from 207.158.206.145: bytes=32 time=375ms TTL=63

Ping statistics for 207.158.206.145:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 375ms, Average = 293ms
----------------------------------------
I want to be using the DNS from the PPP adapter's DNS entry. An NSLookup
confirms that 10.4.2.15 is the DNS server I should be using. However, I am
not. I appear to still be using the local DNS first.

I can ping the internal IP address (10.4.2.66), and it even resolves the DNS
name when I do a ping -a to the internal IP address. However, when I ping
the DNS name it resolves to the public/external IP address.

Everything in this setup is Microsoft - the internal DNS & DHCP server is
one Windows server, the RAS - VPN server is another windows server, the VPN
client is a Windows machine. The remote LAN in this instance is a wireless
router that assigns the local IP and DNS. I can only get DNS names to
properly resolve to the internal IP address under two scenarios:

1. If the local DNS is screwed up and doesn't work, then the VPN client will
use the DNS from 10.4.2.15
2. If you manually put in 10.4.2.15 as your local primary DNS on the VPN
client (and, if you like, the actual local DNS as your SDNS)

posting the result of ipconfig /all may help. Also assuming the remote LAN DHCP will assign IP, DNS to the VPN client.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
I too am having this problem.

I have DNS names that I need to resolve to one IP address internally or when
VPNed, and a different IP address externally. However, when VPNed, the VPN
client is resolving the DNS name to the external IP address.

The VPN client does receive the DNS server from the VPN server, but uses the
local DNS server instead.

If I manually enter in the VPN server's DNS entry as the local DNS entry,
then it starts resolving the correct internal IPs for the VPN client, but
there has to be a more appropriate solution than asking the VPN client to
manually enter in DNS entries on his or her computer.

 

[Guest]

A fellow named Gleo posted an MS KB article in another thread that seems to
have resolved the issue for me:

http://support.microsoft.com/default.aspx?scid=kb;en-us;311218

It involves a registry edit for the VPN client (remote user), but it seems
to work, correctly resolving the public DNS name to the internal IP when
VPNed and to the public IP when not VPNed.

I've also found that wherever the VPN client is, if they receive a public
DNS server as their local DNS (i.e. if the local DHCP is passing out a public
DNS server address) rather than the local gateway as the DNS address (ie.,
the DHCP passing out the internal IP address of the local router/WAP/cable
modem/whatever), then when one VPNs in things seem to resolve correctly. So
you can configure your home network to work, but I'm not sure if airports and
Starbucks and other hotspots pass out a public DNS server to their DHCP
clients or not.

I agree and also suffer from your same situation. I believe the issue
resides in how Microsoft handles traffic that should be sent through the VPN
tunnel. Under the IP properties of the VPN connection and clicking Advanced,
it will bring up the Advanced TCP/IP Settings which on the General Tab a
check box says "Use default gateway on remote network"

However, in the description of this check box, it states "data that cannot
be sent on the local network is forwarded to the dial-up network". This
being said, the DNS server used to connect to the Internet PRIOR to the VPN
connection is LOCAL. According to the description, your workstation will
send the DNS query to the local DNS server (192.168.0.1).

I think this is a security flaw that should be addressed by Microsoft as it
is a form of split tunneling. This setting implies that I can still
communicate with devices on my home network (local) while having a VPN
connection established. This potentially allows someone on the internal
network hijack my workstation while I am connected to the VPN. This is in my
mind NOT disabling split tunneling.

Cisco's VPN client implementation does enforce no split tunneling by
forwarding ALL packets through the tunnel including any packet that would
normally be destined for a local network. This can confuse end users because
when connected to the VPN, they cannot even see anything on their home
network. However, this is truely disabling split tunneling and should be the
way it works.

I am supprised the Microsoft client would allow this and I suspect that
there may be a registry setting to forward ALL packets through an established
tunnel but I have been unsuccessful at finding it. Any help or valid
workaround would be greatly appreciated.

Here is the result of an ipconfig /all. Out of paranoia, I've changed some
of the info, but you should get the gist of the problem:
----------------------------------------------------
C:\Documents and Settings\JWM>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : JWMlaptop
Primary Dns Suffix . . . . . . . : mycompany.corp
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mycompany.corp
se1.client2.attbi.com
mycompany-corp

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : se1.client2.attbi.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG
Network Connection
Physical Address. . . . . . . . . : 00-13-CE-29-AD-D7
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, September 08, 2005
12:18:21 AM
Lease Expires . . . . . . . . . . : Sunday, September 11, 2005
12:18:21 AM

PPP adapter VPNServer:

Connection-specific DNS Suffix . : mycompany-corp
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.4.10.10
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 10.4.10.10
DNS Servers . . . . . . . . . . . : 10.4.2.15

C:\Documents and Settings\JWM>nslookup
*** Can't find server name for address 192.168.0.1: Non-existent domain
Default Server: officeDNSserver.mycompany.corp
Address: 10.4.2.15

exit

C:\Documents and Settings\JWM>ping -a 10.4.2.66

Pinging www.JWM.com [10.4.2.66] with 32 bytes of data:

Reply from 10.4.2.66: bytes=32 time=80ms TTL=126
Reply from 10.4.2.66: bytes=32 time=366ms TTL=126
Reply from 10.4.2.66: bytes=32 time=368ms TTL=126
Reply from 10.4.2.66: bytes=32 time=388ms TTL=126

Ping statistics for 10.4.2.66:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 388ms, Average = 300ms

C:\Documents and Settings\JWM>ping www.JWM.com

Pinging www.JWM.com [207.158.206.145] with 32 bytes of data:

Reply from 207.158.206.145: bytes=32 time=83ms TTL=63
Reply from 207.158.206.145: bytes=32 time=373ms TTL=63
Reply from 207.158.206.145: bytes=32 time=343ms TTL=63
Reply from 207.158.206.145: bytes=32 time=375ms TTL=63

Ping statistics for 207.158.206.145:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 375ms, Average = 293ms
----------------------------------------
I want to be using the DNS from the PPP adapter's DNS entry. An NSLookup
confirms that 10.4.2.15 is the DNS server I should be using. However, I am
not. I appear to still be using the local DNS first.

I can ping the internal IP address (10.4.2.66), and it even resolves the DNS
name when I do a ping -a to the internal IP address. However, when I ping
the DNS name it resolves to the public/external IP address.

Everything in this setup is Microsoft - the internal DNS & DHCP server is
one Windows server, the RAS - VPN server is another windows server, the VPN
client is a Windows machine. The remote LAN in this instance is a wireless
router that assigns the local IP and DNS. I can only get DNS names to
properly resolve to the internal IP address under two scenarios:

1. If the local DNS is screwed up and doesn't work, then the VPN client will
use the DNS from 10.4.2.15
2. If you manually put in 10.4.2.15 as your local primary DNS on the VPN
client (and, if you like, the actual local DNS as your SDNS)

posting the result of ipconfig /all may help. Also assuming the remote LAN DHCP will assign IP, DNS to the VPN client.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
I too am having this problem.

I have DNS names that I need to resolve to one IP address internally or when
VPNed, and a different IP address externally. However, when VPNed, the VPN
client is resolving the DNS name to the external IP address.

The VPN client does receive the DNS server from the VPN server, but uses the
local DNS server instead.

If I manually enter in the VPN server's DNS entry as the local DNS entry,
then it starts resolving the correct internal IPs for the VPN client, but
there has to be a more appropriate solution than asking the VPN client to
manually enter in DNS entries on his or her computer.

:

assuming you have windows RRAS as VPN server, the VPN client takes the server DNS. you may assign another DNS manually.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Anyone found a solution for this? This has been an issue of mine for
quite a while now, too.

Thanks,
Bill