Cannot resolve DNS

  • Thread starter Thread starter Vincent Breton
  • Start date Start date
V

Vincent Breton

Hi all!

I have a problem to resolve DNS through a VPN tunnel.
I don't know if it possible.
I've a "mini" network connect to our principal network through a Tunnel on
internet.
My Win 2000 Server is on our principal network.
I'm trying to reach the server from our "mini" network. I received a DNS
lookup error.
It is possible to reach my server?
If yes, how can I do that?

Thank!
If you need more informations to help me, just ask me...

Mag
 
Vincent Breton said:
Hi all!

I have a problem to resolve DNS through a VPN tunnel.
I don't know if it possible.
I've a "mini" network connect to our principal network through a Tunnel on
internet.
My Win 2000 Server is on our principal network.
I'm trying to reach the server from our "mini" network. I received a DNS
lookup error.
It is possible to reach my server?
Yes.

If yes, how can I do that?
Click to expand...

Well, how all depends on what equipment and software you are using to
faclitate your VPN connectivity. Perhaps you could share a little vital
information like:

Office VPN/Firewall device/software
Remote VPN/Firewall device/softeware

OS versions

etc...
 
In
posted their thoughts said:
Hi all!

I have a problem to resolve DNS through a VPN tunnel.
I don't know if it possible.
I've a "mini" network connect to our principal network through a
Tunnel on internet.
My Win 2000 Server is on our principal network.
I'm trying to reach the server from our "mini" network. I received a
DNS lookup error.
It is possible to reach my server?
If yes, how can I do that?

Thank!
If you need more informations to help me, just ask me...

Mag
Click to expand...

As David said, info on your devices would be helpful.

Also info on how you configured your static routes thru the VPN devices. Can
both subnets communicate? Can you ping by your internal private IPs between
machines in both locations?

As for DNS, the recommendation is to only point to your own servers.

If you have a remote location, depending on the amount of users, you can
setup a DNS server on that remote subnet. If installed on a DC out there,
you can make the zone AD Integrated, just as the central location, so the
info is exactly the same on both DNS and let AD handle replication.
OTherwise, create a secondary of the Primary in your central office. Then
point your clients' DNS addresses in their IP properties to their respective
DNS servers.

If you want Internet name resolution too, use a forwarder that is
individually configured on each DNS server, to point to the ISP's DNS
server. This way AD will work correctly and you get Internet access. Don't
use the ISP's DNS addresses in any internal machines or other problems
*will* arise.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Thank for your answer!

My two subnet are on a Class C address
192.168.1.x (principal network)
192.168.3.x (other site)

The two subnets are linked by 2 cisco router (PIX). I can ping my principal
network from my remote site.
When I configure my network identification and add the domain name, I get
the DNS lookup error.
It don't seem to be able to resolve domain name or something like that.
 
I use a tunnel create with 2 cisco PIX router...
OS version of my client computer is Windows 2000 Pro
I ping each subnet from each site.
1st subnet : 192.168.1.x
2nd subnet : 192.168.3.x

I can ping my server from the remote site but I get a DNS lookup error when
I try to log my user on it.

Thank for your help!

Mag
 
Back
Top