which DNS server would be used?

[djc]

if you are connected remotely to a windows 2000 VPN while also connected to
a local LAN for internet access you would have two adapters each with their
own tcp/ip settings. For example you would have Local Area Connection (your
hard lined NIC) connected to the local lan with its own tcp/ip config,
including its own DNS server entries. And you would have your PPP VPN
adapter with it's own tcp/ip config, including a different DNS server.

example:
local lan connection:
ip: 192.168.1.50
sm: 255.255.255.0
dg: 192.168.1.1
dns: 192.168.1.1

PPP VPN adapter:
ip: 10.10.1.35
sm: 255.255.255.255
dg: 10.10.1.35
dns: 10.10.1.5

which DNS server is used if I were to ping a remote host? the local one or
the PPP one?

 

[Robert L [MS-MVP]]

This is a good question. It depends. In your case (if I were to ping a
remote host), you should use the VPN DNS. The basic rule is the DNS goes
with the Default Gateway.

--
For more and other information, go to http://www.ChicagoTech.net


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.


Robert Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[djc]

ok. Thanks!

This is a good question. It depends. In your case (if I were to ping a
remote host), you should use the VPN DNS. The basic rule is the DNS goes
with the Default Gateway.

--
For more and other information, go to http://www.ChicagoTech.net


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.


Robert Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[Bill Grant]

As well as the DNS IP address, it is a good idea to also include the DNS
suffix in the connection properties. If the network you connect to is using
say mydomain.local as its DNS suffix, include that suffix in the TCP/IP
settings in the connection properties. You will then be able to "see"
machines on the LAN using their simple names like "server1" . If you don't
include it, you would need to use "server1.mydomain.local" .

 

[Robert L [MS-MVP]]

Hi Bill, thank you for the input.

--
For more and other information, go to http://www.ChicagoTech.net


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.


Bob Lin, MS-MVP, MCSE & CNE

Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[djc]

thank you. will do.

As well as the DNS IP address, it is a good idea to also include the DNS
suffix in the connection properties. If the network you connect to is using
say mydomain.local as its DNS suffix, include that suffix in the TCP/IP
settings in the connection properties. You will then be able to "see"
machines on the LAN using their simple names like "server1" . If you don't
include it, you would need to use "server1.mydomain.local" .