DNS Subdomain problem "Simon Abolnar" <Simon.Abolnar[ at ]tscng.net> 6/6/2007 3:46:48 PM We have a DNS server that is also DC. We have domain.net (standard primary type) forward zone which is working OK. We created subdomain for DC (Active directory-integrated primary type) as a new forward zone. subdomain.domain.net. Only our DNS server can resolve subdomain's names. Forwarders for all zones are set to our ISP. Where is the problem, that other DNS servers can't resolve our subdomain's names (non-existing domain). Thanks for help! Simon

Re: DNS Subdomain problem "Herb Martin" <news[ at ]learnquick.com> 6/6/2007 5:14:08 PM "Simon Abolnar" <Simon.Abolnar[ at ]tscng.net> wrote in message news:%23W7EmHFqHHA.3948[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > We have a DNS server that is also DC. > We have domain.net (standard primary type) forward zone which is working > OK. > > We created subdomain for DC (Active directory-integrated primary type) as > a new forward zone. > subdomain.domain.net. Since you made this a separate zone this is NOT a "sub-domain" (in the Microsoft MMC terminology) but rather a CHILD Zone, i.e., a SEPARATE zone with separate replication. > Only our DNS server can resolve subdomain's names. Makes sense unless you have some Secondaries or another AD Integrated DNS server for this same domain to service this zone. What is NOT working that should be? > Forwarders for all zones are set to our ISP. Irrelevant to resolving an internal zone. (But likely correct anyway.) > Where is the problem, that other DNS servers can't resolve our subdomain's > names (non-existing domain). Are they AD Integrated (on DCs) or are they setup as Secondaries? Since you made it a CHILD zone (not a subdomain) it is not going to replicate with the parent zone. Make the other DNS-DCs secondaries or also AD Integrated for this zone. -- Herb Martin, MCSE, MVP http://www.LearnQuick.Com (phone on web site)

Re: DNS Subdomain problem "Simon Abolnar" <Simon.Abolnar[ at ]tscng.net> 6/6/2007 5:52:49 PM Thank you very much for your help! I have solved my problem. NS was wrong in child zone (ns.subdomain.domain.net. instead of ns.domain.net). Simon "Herb Martin" <news[ at ]learnquick.com> wrote in message news:%231f%23Y4FqHHA.3736[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] > > "Simon Abolnar" <Simon.Abolnar[ at ]tscng.net> wrote in message > news:%23W7EmHFqHHA.3948[ at ]TK2MSFTNGP05.phx.gbl... >> We have a DNS server that is also DC. >> We have domain.net (standard primary type) forward zone which is working >> OK. >> >> We created subdomain for DC (Active directory-integrated primary type) as >> a new forward zone. >> subdomain.domain.net. > > Since you made this a separate zone this is NOT a "sub-domain" (in the > Microsoft MMC terminology) but rather a CHILD Zone, i.e., a SEPARATE > zone with separate replication. > >> Only our DNS server can resolve subdomain's names. > > Makes sense unless you have some Secondaries or another AD Integrated > DNS server for this same domain to service this zone. > > What is NOT working that should be? > >> Forwarders for all zones are set to our ISP. > > Irrelevant to resolving an internal zone. (But likely correct anyway.) > >> Where is the problem, that other DNS servers can't resolve our >> subdomain's names (non-existing domain). > > Are they AD Integrated (on DCs) or are they setup as Secondaries? > > Since you made it a CHILD zone (not a subdomain) it is not going to > replicate with the parent zone. > > Make the other DNS-DCs secondaries or also AD Integrated for this > zone. > > -- > Herb Martin, MCSE, MVP > http://www.LearnQuick.Com > (phone on web site) >