Solved

2 subnet DNS Setup

Posted on 2006-07-07
2
331 Views
Last Modified: 2010-04-18
I have a windows 2003 network setup in two locations connected via WAN VPN.   What would be the correct DNS configuration for this setup?  I am starting to see a long logon time in the remote location.

Should I have a DNS Server on both sides and have the 2 servers replicate to each other?  

How should the DC's be setup? Normally I have all PC's / BDC's DNS Set for the DC, and the DC pointed to itself. Should the DC in each location be set to itself and the clients in each subnet set to that DC?  Have everyone pointed to the main DC in the primary location? Sorry rambling...


Thanks,
Scott


0
Comment
Question by:scott_thompson
2 Comments
 
LVL 51

Expert Comment

by:Netman66
Comment Utility
You should have DNS at both locations.  If the zones are AD Integrated, then simply installing DNS on the remote site's DC will create a populate the zones for you.

You should also run DHCP locally so you can hand out the local DNS server address as well as making the remote DC a Global Catalog server.

If you add another DC in the remote location you need to also setup Sites in AD Sites and Services to allow clients to talk with their local servers for authentication.
0
 
LVL 33

Accepted Solution

by:
NJComputerNetworks earned 500 total points
Comment Utility
example of settings on clients and servers:

Server Name: SERVERDC1
IP: 10.10.10.5
Subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS1: 127.0.0.1 or 10.10.10.5  <--- Make sure the DC points to itself for DNS resolution (Do NOT point to the ISP DNS servers)
DNS2: 20.20.20.6

Server Name: SERVERDC2
IP: 20.20.20.6
Subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS1: 10.10.10.5  <--- Make sure the DC points to the first DC for DNS resolution (Do NOT point to the ISP DNS servers)
DNS2: 20.20.20.6 or 127.0.0.1

Client Name or Memberserver: Desktop1
IP: 10.10.10.51
Subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS1: 10.10.10.5  <--- Make sure the client points to the closest DC for DNS resolution (Do NOT point to the ISP DNS servers)
DNS2: 20.20.20.6  <--- Make sure the client point to the second closest DC for DNS resolution



After you have verified that replication has completed successfully, DNS may be configured on each Domain Controller in either of two ways, depending on the requirements of the environment. The configuration options are:• Configure the Preferred DNS server in TCP/IP properties on each Domain Controller to use itself as Primary DNS Server. • Advantages:
Ensures that DNS queries originating from the Domain Controller will be resolved locally if possible. Will minimize impact of Domain Controller’s DNS queries on the network
• Disadvantages:
Dependant on Active Directory replication to ensure that DNS zone is up to date. Lengthy replication failures may result in an incomplete set of entries in the zone.  
 
• Configure all Domain Controllers to use a centralized DNS server as their Preferred DNS Server. • Advantages:• Minimizes the reliance on Active Directory replication for DNS zone updates of Domain Controller locator records. This includes faster discovery of new or updated Domain Controller locator records, as replication lag time is not an issue.
• Provides a single authoritative DNS server, which may be useful when troubleshooting Active Directory replication issues
 
• Disadvantages:• Will more heavily utilize the network to resolve DNS queries originating from the Domain Controller
• DNS name resolution may be dependant on network stability; loss of connectivity to the Preferred DNS server will result in failure to resolve DNS queries from the Domain Controller. This may result in apparent loss of connectivity, even to locations that are not across the lost network segment.
 
 
http://support.microsoft.com/?kbid=825036
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
Excel styles will make formatting consistent and let you apply and change formatting faster. In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. You'll also learn how to use your custo…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now