Thanks a lot Dean. So tell me if I've got this right, so I'll know that I've finally wrapped my brain around it:
1. If I configure the baz.foo.com child domain, but make no changes to my DNS structure, then clients in the baz.foo.com domain will still point to the nameserver in foo.com. (Assuming that we're not all pointing out to an ISP DNS or something silly, obviously.) 2. If I want baz.foo.com to be responsible for its own DNS, I'll install a DNS server somewhere in the baz.foo.com domain, create a zone for baz.foo.com on the baz.foo.com NS, and create a delegation on the foo.com NS. At which point I can direct the baz.foo.com clients to the local NS for name resolution. 3. I need to configure some way for baz.foo.com to resolve queries for the rest of the world, either using a stub zone or some type of forwarding. 4. Stub/zones conditional forwarding will prevent the name resolution stupidity of a baz.foo.com client needing to go all the way out to the Internet and back just to locate a resource in foo.com. Hmmm, now try this one on for size: If I install DNS on the first DC for baz.foo.com, does the baz.foo.com zone get created locally automagically? Or do I still need to manually do the stuff in item 2 above? Thanks so much! Laura List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
