Question

Locked

Parent-Child Domains

By black_roads ·
Hi,

Ive created a parent domain named abc.com (192.168.0.1/24) and a child domain xyz.abc.com (192.168.1.1/24) by using the DNS of the parent domain. All them pass to a router w/c link them together. The problem is when im in the parent domain (abc.com) Active Directory and trying to connect to my child domain. it cannot be contacted to. while when im in the child domain (xyz.abc.com) AD and trying to connect to parent domain everything seems fine. I want to know why is this?

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Sounds like either DNS or AD domains and Trusts issue

by CG IT In reply to Parent-Child Domains

If DNS doesn't have records for the child domain [seperate subnet]and you have DCs and DNS for the child domain on the child domains subnet, that probably is the problem. No communications between DNS and DCs on the child domain subnet.

If you don't have seperate DCs and DNS for the child domain, then you probably should check that your child domain shows up in AD domains and trusts and as a suggestion create a site for the child domain in AD sites and services.

See if that works

Collapse -

What kind of router is between the subnets?

by Churdoo In reply to Parent-Child Domains

What kind of router do you have between the 2 subnets? If it's an off-the-shelf SOHO router, the default configuration is "gateway" mode with a WAN side and a LAN side. NAT would prevent inbound communication from the WAN side, i.e. the symptoms that you've described.

Collapse -

Was my first thought though there is comm

by CG IT In reply to What kind of router is be ...

from child to parent but not parent to child. I assumed that DNS isn't running on the child domain nor is there a DC on the child domain. The parent domain DCs and DNS servers host the zone and AD.

So yes a router might cause a traffic problem between the parent and the child but it also should cause the same problem from child to parent. Since this isn't the case, he might not have associated a subnet for the child domain [site] in AD Sites and Services. [also check that the child domain shows up in AD Domains and Trusts].

Still your probably right in that the router is blocking traffic or some firewall settings are blocking traffic.

Collapse -

Child to parent

by Churdoo In reply to Was my first thought th ...

I'm thinking that since communication from child to parent is happening, then it's the child domain that's on the LAN side of a SOHO router. The outbound requests of the child domain can be responded to by the parent because of NAT but only in response to a request by the child while NAT holds the respective ports open. Unsolicited inbound traffic by the parent would be blocked by NAT.

If there's a second SOHO router serving the ISP connection, then both subnets would still be able to browse the internet -- the child domain/subnet traffic would be double-NAT'd, but would still work for generic www browsing.

At least that's my thinking. I understand what you're saying, and any or all of the things that you mentioned could also be wrong, as there wasn't enough pertinent information given.

Back to Software Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums