ForestDNSZones and DomainDNSZones from two different domains.

prod environment: root/child domain
dev environment: single domain 1 way trust prod env.

both prod , dev environments pointing same dns servers.

we installed microsoft crm on prod , able installed it. when tried install microsoft crm on dev environment, kept on failing @ end of installation. ran network monitor , failed when tried query forestdnszones.

i ran:
 dnscmd /directorypartitioninfo forestdnszones.domaindev.com
 dnscmd /directorypartitioninfo domaindnszones.domaindev.com

and received message saying not exist see both forestdnszones , domaindnszones under domaindev. decided delete both application partitions , recreated following command:

dnscmd dnsserver1 /createbuiltindirectorypartitions domaindnszones.domaindev.com
dnscmd dnsserver1 /createbuiltindirectorypartitions forestdnszones.domaindev.com

i recreated domaindnszones , forestdnszones , able execute these commands:

 dnscmd /directorypartitioninfo forestdnszones.domaindev.com
 dnscmd /directorypartitioninfo domaindnszones.domaindev.com

i tried microsoft crm install again installed.

i ran microsoft adrap against development environemt , getting warning:

the following application partition contains invalid fsmo role owner:
partition:  cn=infrastructure,dc=domaindnszones,dc=domaindev,dc=com
fsmo:  n/a

adsiedit, tried connect dc=domaindnszones,dc=domaindev,dc=com or dc=forestdnszones,dc=domaindev,dc=com , got error:
  operation failed. error code: 0x202b
  referral returned server.

questions:
1. know install worked did correctly created domaindnszones , forestdnszones?
2. how fix invalid fsmo role owner warning?
3. prod , dev have own ad sites. dev zone, notice domaindnszones , forestdnszones sites contains prod sites. should contain dev sites?
4. adsiedit, went cn=configuration,dc=domainprod,dc=com cn=partitions , see both domaindnszones , forestdnszones records both domaindev , domainprod. correct? should dev in partition located in domaindev?
 

 

thanks clarification. have 2 forests.

i believe should re-think dns design in regards how 2 resolving each other. in production forest, either create dns delegation child, blog posted above shows how, or use forest root dns servers domains.

as resolution between 2 forests, keep them separate , not use production forest both forests. believe best option make rsure resolution works between them are use either conditional forwarder on production development domain, , vice versa, or use stub zone, or secondary zones of each each forest root dns.

this way each forest remains clean.

regarding partitions, if manually create zone on dc of zone exists ad integrated zone in respective scope, introduce duplicate. posted above (shown below), it appears created duplicate of domaindev.com in 2 different partitions. this not desireable result. must careful working ad integrated zones in manner that appears you're trying do. 

dnsserver -   forward lookup zones - domaindev.com - forestdnszones - _sites - <all sites>

dnsserver -   forward lookup zones - domaindev.com - domaindnszones - _sites - <all sites>

ace

 

---

ace fekay
mvp, mct, mcitp ea, mcts windows 2008 & exchange 2007 & exchange 2010, exchange 2010 enterprise administrator, mcse & mcsa 2003/2000, mcsa messaging 2003
microsoft certified trainer
microsoft mvp - directory services

this posting provided as-is no warranties or guarantees , confers no rights.

Windows Server  >  Network Infrastructure Servers