Multiple critical errors in DNS log after installing AD

Tech-Archive recommends: Fix windows errors by optimizing your registry



I have a Win2003 server that I set up as a secondary DNS server about a week
ago. It's been running fine - getting new versions of the zone, etc.
Today I installed Active Directory on it to act as a second domain
controller (I've had a series of other DCs die on me recently and have been
tempting fate too long).

AD installed ok and it appears that replication is successful.

Now, however, I get multiple messages in the DNS server event log:
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4015
Date: 5/2/2006
Time: 11:01:07 AM
User: N/A
Computer: GEORGE
Description:
The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly. The extended error
debug information (which may be empty) is "000021A2: SvcErr: DSID-030A09EE,
problem 5001 (BUSY), data 0". The event data contains the error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 33 00 00 00 3...

Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 4514
Date: 5/2/2006
Time: 11:01:07 AM
User: N/A
Computer: GEORGE
Description:
The DNS server detected that it is not enlisted in the replication scope of
the directory partition DomainDnsZones.cerc.local. This prevents the zones
that should be replicated to all DNS servers in the cerc.local domain from
replicating to this DNS server. For information on how to add a DNS server to
the replication scope of an application directory partition, please see Help
and Support.

To create or repair the domain-wide DNS directory partition, open the the
DNS console. Right-click the applicable DNS server, and then click 'Create
Default Application Directory Partitions'. Follow the instructions to create
the default DNS application directory partitions. For more information, see
'To create the default DNS application directory partitions' in Help and
Support.
The error was 9002.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2a 23 00 00 *#..

I've tried created the dfault DNS application directory partitions, but that
doesn't seem to do anything.

I'm thinking that this has something to do with the properties of my zone -
right now, on the primary DNS server, the zone cerc.local is ste as an active
directory-integrated zone, and replication is set to "all domain controllers
in the AD domain" - should I be changing this?

Any help would be appreciated. Before my last DC died, I had replication
issues there as well, so I do think something is screwy on the DC/primary DNS
server.
thanks
.



Relevant Pages

  • Re: Local Delivery is not sending to one recipient in Exchange Ser
    ... The DNS server was unable to open zone rickkochoil in the Active Directory ... Errors in File Replication Service: ... Running partition tests on: ForestDnsZones ...
    (microsoft.public.exchange.admin)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... I did run dcdiag on all DCs, ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... Keep the zone with forest wide ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... switch back to AD with Forest wide, and then put the DNS service ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... Keep the zone with forest wide ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)