Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 490
  • Last Modified:

Creating DNS zones for Parent - Child Domains

Here is the situation. I have a root domain (purely for administration) and 2 child domains( one in Greece & US) each with multiple sites. The root domain & child domain reside in same site.

 Within the US Child domain, I have 2 sites (atlanta & NYC), I want the DC in those locations to host DNS for their clients and have all internet traffic generated to be directed to the local ISP

How is DNS set up in the Parent domain to reflect this and also how is it setup in the child domain to be site specific?
0
broberc6
Asked:
broberc6
  • 2
  • 2
  • 2
  • +1
3 Solutions
 
NJComputerNetworksCommented:
"Within the US Child domain, I have 2 sites (atlanta & NYC), I want the DC in those locations to host DNS for their clients and have all internet traffic generated to be directed to the local ISP"

The internet traffic (web browsing) will traverse using your ROUTER rules...and not DNS rules.  In other words, the client will use thier TCP/IP Gateway settings to get out to the internet.  So, as long as you routers are setup properly, the clients will use the local ISP internet connection.

You can use this command to test...(from a command prompt)

TRACERT www.yahoo.com <enter>  

This will show you the path the client is using to get out to the internet.
0
 
broberc6Author Commented:
How would the zones in the parent domain and the child domain?
0
 
NJComputerNetworksCommented:
"How would the zones in the parent domain and the child domain?"  Sorry, I don't understand what you mean... its like saying "how would the dog in the house?"
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Netman66Commented:
On the Parent domain:

All zones should be AD Integrated.
The _msdcs zone should have a replication scope of "To all DNS servers in the Forest"
The domain.local zone should have a replication scope of "To all DNS servers in the domain"

On each child:

The _msdcs zone should propogte automatically from the parent.
The child.domain.local zone should remain local to the domain only.

On the Forwarders tab on each of the child domain's DNS servers:

Setup Conditional Forwarding for the Parent domain to forward to that DNS server.

On the Forwarders tab of the parent DNS server:

Setup Conditional Forwarding for each of the child domains and forward to the correct DNS server.


On the Forwarders tab of ALL DNS servers - any other domain - send to the Local ISP.


ALL client computers should contain only their local DNS server's address and nothing else.

Each DC should be a GC.

Hope this helps.
NM
0
 
Chris DentPowerShell DeveloperCommented:

Just a couple of questions / comments on the proposed setup:

> On the Forwarders tab on each of the child domain's DNS servers:
> Setup Conditional Forwarding for the Parent domain to forward to that DNS server.

Wny not just configure the Parent Zone to replicate it's own domain.local to the entire forest. The zone should be small anyway and changes are going to be minimal. It's size compared to the usual GC type replication is also pretty insignificant so wouldn't burden anything. Only applies if Windows 2003 is being used.

> On the Forwarders tab of the parent DNS server:
> Setup Conditional Forwarding for each of the child domains and forward to the correct DNS server.

Unnecessary. The Parent domain should know about the child domains as they should be within it's DNS hierarchy. That is, the parent zone should have Name Server records for each sub-domain (or child domain). If there are Name Server records you don't need Forwarders as it knows exactly where to send the request already.

Chris
0
 
Netman66Commented:
You could make the domain zones part of the Application partition so they replicate to all servers in the Forest, sure.  Most of the time there is no need for domains (internally) to resolve anything in the other domains except the servers so why make the local DNS server authoritative for the zone?  This is why I stated it the way I did, with Conditional Forwarding.

It's not as much about the parent knowing the child as it is about the child knowing about the parent.

0
 
Chris DentPowerShell DeveloperCommented:

Oh I agree completely. We just switched from using Forwarders for our domain to replicating the root domain to the entire forest... nice and neat :)

Chris
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now