Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LAN to LAN DNS resolution

Status
Not open for further replies.

tty0

Programmer
Nov 13, 2002
108
GB
Hi,
quick problem,
This is the setup:
Network A has many clients and an sbs2003 server, the internet is managed by a VPN firewall router and has its own internet connection.

Network B is exactly the same as network A but at a different location and both networks are connected via a VPN tunnel.

This is the problem:
each network resolves internally and resolves internet addresses. However! network A will not resolve hostnames on network B and vice versa.

Help!! Pleaseeeee.



'mi casa es su casa'
]-=tty0=-[
 
Not enough information. What are the names of the primary zones and which site are they being hosted in (which server holds the primary zone)?

Start, Help. You'll be surprised what's there. A+/MCP/MCSE/MCDBA
 
neither are set to primary

server1.networkA.local runs its own dns

server1.networkB.local runs its own dns

neither dns are aware of the other. Im sure its as simple as forwarding dns records between servers or making one dns server primary and secondary.

no clients on the opposing site can resolve dns for the opposing network

'mi casa es su casa'
]-=tty0=-[
 

Yes, you can forward but that invokes a request everytime, even if it is cache I believe.

A better solution is to make each DNS server secondaries of
each other. DNS then would manage the transfers, and
requests would stay on their own side.

I am a Unix/BIND guy, but I am pretty sure that W2K DNS supports the secondary concept as BIND does.

gene
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top