Solved

Domain Controllers and DNS for office location and DR site connected by MPLS network

Posted on 2014-09-17
3
221 Views
Last Modified: 2014-10-16
I currently have 2 office locations and a DR site that are all connected via an MPLS network.  Each location is on its on subnet as follows:

DR site 192.168.3.xxx
Main Office 192.168.100.xxx
Fleet Office 192.168.3.xxx

I am trying to figure out how to setup the network a the new combined location's far as DC's and DNS as well as DHCP.  Should I just combine them into the same subnet 192.168.200.xxx making sure that I have allocated enough IPS as needed? The DR site will stay on the same subnet its on now 192.168.3.xxx
How many DC's do I really need?  I have two at the DR site and 2 at the new combined location currently.  Any suggestions would be appreciated!
0
Comment
Question by:Michael Collins
[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
  • 2
3 Comments
 
LVL 39

Expert Comment

by:Aaron Tomosky
ID: 40330360
I would not suggest combining subnets across sites. Use at least /24 for each site. Ideally you want one dc at each physical location to minimize traffic over the Mpls. Active directory sites and services is what you setup to tell each subnet which site it belongs in and therefore which dc to use and how the DCs replicate
0
 

Author Comment

by:Michael Collins
ID: 40330657
Okay, thanks for you input. What about DNS?  The DR site is a .local domain and the new combined office is xxx.com  The xxx.com domain is active directory-integrated primary and the xxx.local domain is secondary, both are forward lookup zones in DNS.  All Dc's have both zones loaded on them as such, this is the way the DNS was setup prior to my being here, but I am having some slight DNS issues with server name resolution.  Is this a preferred way to have the DNS setup or should it be done differently?  Thanks
0
 
LVL 39

Accepted Solution

by:
Aaron Tomosky earned 500 total points
ID: 40330741
Normally I would just put each zone on its servers and use a conditional forwarder, but I'm not sure if that works with .local. Personally I always use a subdomain of a registered real domain like corp.domain.com
Maybe someone else will have experience with .local and conditional forwarders.
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
An article on effective troubleshooting
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

740 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