June's Course of the Month is now available! Every 10 seconds, a consumer gets hit with ransomware. Refresh your knowledge of ransomware best practices by enrolling in this month's complimentary course for Premium Members, Team Accounts, and Qualified Experts.
Course Of The Month
1 day, 16 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Child domain in existing tree
Posted on 2004-09-17
I have a windows 2000 domain with Active directory installed. The domain (rites.com) is installed in Location A. Recently I installed a new child domain (sales.rites.com) in the existing tree at a new Location B. Both the locations are separated by a WAN link (T1). I have created an IPSEC tunnel between the two offices for connectivity. While installing the child domain I created the first DC (A1WSITE2-1) as a child domain to the existing root domain rites.com. Right now the DC (A1WSITE1-2) is pointing to the DNS from the root domain (both preferred and secondary). Do I need to install a local DNS server in location B for sales.rites.com? Can I point all my servers to the DNS server in the root domain? Is it a recommended setting.
Thanks
Ripul
Thanks
Ripul
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
5 Comments
The best recommendation is to have a least one DNS server & DC in every single location.
Why ? simple...what if somehow SiteA lost connection with SiteB ? How are clients from SiteB going to get DNS responses from a DNS server they cannot reach ?
The best thing is to define a DNS server in your SiteB, as a secondary zone...so It will replicate all the entries from your root domain....and don't forget to point your SiteB's computers to have your SiteB DNS Server as their primary DNS ;-)
You'll also reduce traffic for DNS queries between SiteA and SiteB, and you'll have a complete DNS fault tolerance Site.
Hope it helps !!
Why ? simple...what if somehow SiteA lost connection with SiteB ? How are clients from SiteB going to get DNS responses from a DNS server they cannot reach ?
The best thing is to define a DNS server in your SiteB, as a secondary zone...so It will replicate all the entries from your root domain....and don't forget to point your SiteB's computers to have your SiteB DNS Server as their primary DNS ;-)
You'll also reduce traffic for DNS queries between SiteA and SiteB, and you'll have a complete DNS fault tolerance Site.
Hope it helps !!
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Make the most of your online learning experience.
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers.
Hopes this gives you ideas on visualizing your data in new ways ~
Create a calculated field in a query:
…
Suggested Courses
Course of the Month1 day, 16 hours left to enroll
717 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.