Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » Re: Problem creating AD zones
Re: Problem creating AD zones [message #156321] Mon, 15 June 2009 03:53 Go to next message
meiweb(nospam)  is currently offline meiweb(nospam)  Germany
Messages: 1307
Registered: July 2009
Senior Member
Hello Taz1972,

You mean DNS zones i assume. Is this the first 2003 DNS server in the network?
chekc this article:
http://support.microsoft.com/kb/938459

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hi,
>
> We recently installed a new server 2003 DC at one of our sites in the
> far east.
>
> But when I try to create a new forward zone, I get the message:
>
> "The zone cannot be replicated to all DNS servers in the (null) Active
> Directory domain because the required application directory partition
> does not exist. Only Enterprise Administrators have the appropriate
> permissions to create an application directory partition."
>
> Why am I getting this error, and more importantly what are the exact
> steps needed to fix it? Whats strange is that we did not get this
> error when creating other sites, but now this message has started to
> pop up when trying to create both forward and reverse AD integrated
> zones. Could this mearly be a replication problem or something? We
> have a fully functional 2003 environment.
>
> I am an enterprise admin, but I need to pointers on how to creeate an
> AD partition step-by-step.
>
> Thanks,
> Taz
Re: Problem creating AD zones [message #156333 is a reply to message #156321] Mon, 15 June 2009 09:26 Go to previous messageGo to next message
Taz1972  is currently offline Taz1972
Messages: 18
Registered: October 2009
Junior Member
Hi Meinolf,

No, this is not the first DC in the forest. It is just another DC we
installed on another site - a BDC if you will.

I will check the article and let you know.

Thanks,
Taz


"Meinolf Weber [MVP-DS]" wrote:

> Hello Taz1972,
>
> You mean DNS zones i assume. Is this the first 2003 DNS server in the network?
> chekc this article:
> http://support.microsoft.com/kb/938459
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Hi,
> >
> > We recently installed a new server 2003 DC at one of our sites in the
> > far east.
> >
> > But when I try to create a new forward zone, I get the message:
> >
> > "The zone cannot be replicated to all DNS servers in the (null) Active
> > Directory domain because the required application directory partition
> > does not exist. Only Enterprise Administrators have the appropriate
> > permissions to create an application directory partition."
> >
> > Why am I getting this error, and more importantly what are the exact
> > steps needed to fix it? Whats strange is that we did not get this
> > error when creating other sites, but now this message has started to
> > pop up when trying to create both forward and reverse AD integrated
> > zones. Could this mearly be a replication problem or something? We
> > have a fully functional 2003 environment.
> >
> > I am an enterprise admin, but I need to pointers on how to creeate an
> > AD partition step-by-step.
> >
> > Thanks,
> > Taz
>
>
>
Re: Problem creating AD zones [message #156334 is a reply to message #156333] Mon, 15 June 2009 10:18 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Taz1972" <Taz1972@discussions.microsoft.com> wrote in message
news:181746C2-E94F-4320-828D-906DDA5D2F14@microsoft.com...
> Hi Meinolf,
>
> No, this is not the first DC in the forest. It is just another DC we
> installed on another site - a BDC if you will.
>
> I will check the article and let you know.
>
> Thanks,
> Taz

Actually the term BDC is associated with NT4. This new DC would be a
"replica" DC.

Are all DCs 2003? If not, were any of the zone properties regarding
replication scope, changed?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay
Re: Problem creating AD zones [message #156375 is a reply to message #156334] Tue, 16 June 2009 04:38 Go to previous messageGo to next message
Taz1972  is currently offline Taz1972
Messages: 18
Registered: October 2009
Junior Member
I followed the instructions in the linked article but still got the same error.

However what I did was change the 'active directory zone replication scope'
when creating dns zones to 'all domain controllers in the active directory
domain .....' This seems to have solved the issue as I no longer get the
error anymore. It also makes sense since we only host dns on DC's in our
domain.

But has this really solved the issue completely, or will we have any
unexpected problems later?

Thanks,
Taz


"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "Taz1972" <Taz1972@discussions.microsoft.com> wrote in message
> news:181746C2-E94F-4320-828D-906DDA5D2F14@microsoft.com...
> > Hi Meinolf,
> >
> > No, this is not the first DC in the forest. It is just another DC we
> > installed on another site - a BDC if you will.
> >
> > I will check the article and let you know.
> >
> > Thanks,
> > Taz
>
> Actually the term BDC is associated with NT4. This new DC would be a
> "replica" DC.
>
> Are all DCs 2003? If not, were any of the zone properties regarding
> replication scope, changed?
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
> aceman@mvps.RemoveThisPart.org
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> "Efficiency is doing things right; effectiveness is doing the right
> things." - Peter F. Drucker
> http://twitter.com/acefekay
>
>
>
>
>
Re: Problem creating AD zones [message #156389 is a reply to message #156375] Tue, 16 June 2009 09:47 Go to previous message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Taz1972" <Taz1972@discussions.microsoft.com> wrote in message
news:EC498CC4-2967-4BCF-8CAB-8BAB6778CF0E@microsoft.com...
>I followed the instructions in the linked article but still got the same
>error.
>
> However what I did was change the 'active directory zone replication
> scope'
> when creating dns zones to 'all domain controllers in the active directory
> domain .....' This seems to have solved the issue as I no longer get the
> error anymore. It also makes sense since we only host dns on DC's in our
> domain.
>
> But has this really solved the issue completely, or will we have any
> unexpected problems later?
>
> Thanks,
> Taz

Interesting. I think there may have been a zone replication scope mismatch.
If there was, it would have been due to different replication scope settings
on the two DCs for the same zone, which essentially would cause a dupe zone
condition in the AD database. Glad you got this to work, but what I would
like you to do is to find out if tehre is a dupe zone condition. Read the
following with what this means, how it may have occured, and instructions to
find out, and there is, delete the dupes.

============================================================ ==========================================
Conflicting or duplicate AD Integrated DNS zones
By Ace Fekay, MCSE 2003, MCT

You may have a duplicate zone if a zone either exists in both the Domain NC
and one of the Application Partitions, if you get an unusal error message
stating, "The name limit for the local computer network adapter card was
exceeded," or you installed DNS on another DC and manually created the AD
zone and didn't wait for it to automatically populate.

Dupe zone errata:
A quick explanation: When you have an AD integrated zone, the DNS data is
stored in the actual AD database and is replicated to all DCs and will be
available to any DC that has DNS installed, depending on the zone
replication scope setting. If rep scope is set to the bottom button, it will
be store in the DomainNC partition of the AD database and compatible with
Windows 2000. If the middle button, it will be stored in the DomainDnsZones
and only works with Windows 2003 and newer DCs. These two scope types will
be replicated to all DCs only in the domain it exists in. The third type,
the top buttton, is stored in the ForestDnsZones application partition and
is available to ALL DCs in the whole forest. The data in any of the AD
integrated zone types are truly secured since you can;t get at them without
the proper tools.

If you have an AD integrated zone existing on a DC and you install DNS on
another DC in the domain or forest, depending what zone type, it will
automatically appear on the new DNS installation without any interaction on
your part. If you attempted to manually create the zone, then you pretty
much just introduced a duplicate in the AD database, which will cause
problems and other issues as well.

A Primary or Secondary zone that is not stored in AD is stored in a text
file in the system32\dns folder. This type of zone storage has nothing to do
with the above types ONLY unless it is truly a secondary with the Master
being a DC transferring a copy of the zone. This types of zone storage is
obviously not secure.

Now **IF** you did manually create a zone on one DC while it already existed
on another DC, then you may have a duplicate. If this is the case, you can
use ADSI Edit and look for zone data that starts with a "CNF..." in front of
it. Delete them and you;re good to go.

Under Windows 2000, the physcial AD database is broken up into 3 logical
partitions, the DomainNC (Domain Name Context, or some call the Domain Name
Container), the Configuration Partition, and the Schema Partition. The
Schema and Config partitions replicate to all DCs in a forest. However, the
DomainNC is specific only to the domain the DC belongs to. That's where a
user, domain local or global group is stored. The DomainNC only replicates
to the DCs of that specific domain. When you create an AD INtegrated zone in
Win 2000, it gets stored in the DomainNC. This causes a limitation if you
want this zone to be available on a DC/DNS server that belongs to a
different domain. The only way to get around that is for a little creative
designing using either delegation, or secondary zones. This was a challenge
for the _msdcs zone, which must be available forest wide to resolve the
forest root domain, which contains the Schema and Domain Name Masters FSMO
roles.

In Windows 2003, there were two additional partitions added, they are called
the DomainDnsZones and ForestDnsZones Application Partitions, specifically
to store DNS data. They were conceived to overcome the limitation of Windows
2000's AD Integrated zones. Now you can store an AD Integrated zone in
either of these new partitions instead of the DomainNC. If stored in the
DomainDnsZones app partition, it is available only in that domain's
DomainDnsZones partition. If you store it in the ForestDnsZones app
partition, it will be available to any DC/DNS server in the whole forest.
This opens many more design options. It also ensures the availability of the
_msdcs zone to all DCs in the forest. By default in Win 2003, the _msdcs
zone is stored in the ForestDnsZones application partition.

When selecting a zone replication scope in Win2003, in the zone's
properties, click on the "Change" button. Under that you will see 3 options:
To choose the ForestDnsZones:
"To all DNS servers in the AD forest example.com"

To choose DomainDnsZones:
"To all DNS servers in the AD domain example.com"

To choose the DomainNC (only for compatibility with Win2000):
"To all domain controllers in the AD domain example.com"


If you have a duplicate, that's indicating there is a zone that exists in
the DomainNC and in the DomainDnsZones Application partition. This means at
one time, or currently, you have a mixed Win2000/2003 environment and you
have DNS installed on both operating systems. On Win2000, if the zone is AD
Integrated, it is in the DomainNC, and should be set the same in Win2003's
DC/DNS server to keep compatible. Someone must have attempted to change it
in Win2003 DNS to put it in the DomainDnsZones partition no realizing the
implications, hence the duplicate. In a scenario such as this where you want
to use the Win2003 app partitions, you then must insure the zone on the
Win2003 is set to the DomainNC, then uninstall DNS off the Win2000 machine,
then once that's done, you can then go to the Win2003 DNS and change the
partition's replication scope to one of the app partitions.

In ADSI Edit, you can view all five partitions. You were viewing the app
partitions, but not the main partitions. You need to add the DomainNC
partition in order to delete that zone. But you must uninstall DNS off the
Win2000 server first, unless you want to keep the zone in the DomainNC. But
that wouldn't make much sense if you want to take advantage of the _msdcs
zone being available forest wide in the ForestDnsZones partition, which you
should absolutley NOT delete. I would just use the Win2003 DNS servers only.

In ADSI Edit, rt-click ADSI Edit, connect to, in the Connection Point click
on "Well known Naming Context", then in the drop-down box, select "Domain".
Drill down to CN=System. Under that you will see CN=MicrosoftDNS. You will
see the zone in there.

But make sure to decide FIRST which way to go before you delete anything.

To view the DomainDnsZones or the ForestDnsZones partitions, follow these
steps:

[ForestDNSZones]
Click Start, click Run, type adsiedit.msc, and then click OK.
In the console tree, right-click ADSI Edit, and then click Connect to.
Click Select or type a Distinguished Name or Naming Context, type the
following text in the list, and then click OK:
DC=ForestDNSZones, DC=contoso, DC=com
In the console tree, double-click DC=ForestDNSZones, DC=contoso, DC=com.
Double-click CN=MicrosoftDNS, and click the zone (contoso.com). You should
now be able to view the DNS records which exist in this DNS partition. If
you desire to remove this partition, right-click on contoso.com and then
click Delete.

Note Deleting a zone is a destructive operation. Please confirm that a
duplicate zone exists before you perform a deletion.
If you have deleted a zone, restart the DNS service. To do this, follow
these steps:
Click Start, point to All Programs, point to Administrative Tools, and then
click DNS.
In the console tree, right-click contoso.com, point to All Tasks, and then
click Restart.

[DomainDNSZones]
Click Start, click Run, type adsiedit.msc, and then click OK.
In the console tree, right-click ADSI Edit, and then click Connect to.
Click Select or type a Distinguished Name or Naming Context, type the
following text in the list, and then click OK:
DC=DomainDNSZones,DC=contoso,DC=com.
In the console tree, double-click DC=DomainDNSZones,DC=contoso,DC=com
Double-click CN=MicrosoftDNS, and click the zone (contoso.com). You should
now be able to view the DNS records which exist in this DNS partition. If
you desire to remove this partition, right-click on contoso.com and then
click Delete.

Note Deleting a zone is a destructive operation. Please confirm that a
duplicate zone exists before you perform a deletion.
If you have deleted a zone, restart the DNS service. To do this, follow
these steps:
Click Start, point to All Programs, point to Administrative Tools, and then
click DNS.
In the console tree, right-click contoso.com, point to All Tasks, and then
click Restart.

Some reading for you...

Directory Partitions:
http://www.microsoft.com/resources/documentation/Windows/200 0/server/reskit/en-us/distrib/dsbg_dat_favt.asp

kbAlertz- (867464) - Explains how to use ADSI Edit to resolve app partitions
issues:
http://www.kbalertz.com/kb_867464.aspx


How to fix it?
-------------

What I've done in a few cases with my clients that have issues with
'duplicate' zone entries in AD (because the zone name was in the Domain NC
(Name Container) Partition, and also in the DomainDnsZones App partition),
was first to change the zone on one of the DCs to a Primary zone, and
allowed zone transfers. Then I went to the other DCs and changed the zone to
a Secondary, and using the first DC as the Master. Then I went into ADSI
Edit, (from memory) under the Domain NC, Services, DNS, and deleted any
reference to the domain name. Then I added the DomainDnsZones partition to
the ADSI Edit console, and deleted any reference to the zone name in there
as well. If you see anything saying something to the extent of a phrase that
says
"In Progress...." or "CNF" with a long GUID number after it, delete them
too. Everytime
you may have tried tochange the replication scope, it creates one of them.
Delete them all.

Then I forced replication. If there were Sites configured, I juggled around
the servers and subnet objects so all of the servers are now in one site,
then I forced replication (so I didn't have to wait for the next site
replication schedule). Once I've confirmed that replication occured, and the
zones no longer existed in either the Domain NC or DomainDnsZones, then I
changed the zone on the first server back to AD Integrated, choosing the
middle button for it's replication scope (which puts it in the
DomainDnsZones app partition). Then I went to the other servers and changed
the zone to AD Integrated choosing the same replication scope. Then I reset
the sites and subnet objects, and everything was good to go.

Keep in mind, I left the _msdcs... zone alone, since that wasn't causing any
problems and is located in the ForestDnsZones (default) in all of my client
cases I've come across with so far.

It seems like alot of steps, but not really. Just read it over a few times
to get familiar with the procedure. You may even want to change it into a
numbered step by step list if you like. If you only have one DC, and one
Site, then it's much easier since you don't have to mess with secondaries or
play with the site objects.

I hope that helps!
============================================================ ==========================================
Ace
Previous Topic:disable gpo
Next Topic:GP errors
Goto Forum:
  


Current Time: Wed Oct 18 01:38:22 EDT 2017

Total time taken to generate the page: 0.03973 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software