EventID 4521 warning after SP2 upgrade

Sponsored Links

After installing SP2 via WSUS, both of my DNS servers started to register
EventID 4521, error 9002. Description: The DNS server encountered error 9002
attempting to load zone . from Active Directory. The DNS server will attempt
to load this zone again on the next timeout cycle.

Updates to the three zones I have seem to be showing up on both servers so I
don't know which zone isn't loading. I don't think the error message knows
either, it's probably suppost to display the zone name in the description.

The DNS server encountered error 9002
> attempting to load zone . from Active Directory. The DNS server will
> attempt
> to load this zone again on the next timeout cycle.


It may be talking about the "." (dot) forward lookup zone that is created by
default and in most DNS setups is deleted to prevent the DNS server from
thinking it's a root server and allowing forwarders to be set up.


See How to Remove the Root DNS Zone in this article:
http://support.microsoft.com/kb/323380/en-us

hth
DDS


"Ron" <ron-awa@community.nospam> wrote in message
news:A3D8B4EE-C8E8-42A2-8FA4-23BD3CD450EA@microsoft.com...
> After installing SP2 via WSUS, both of my DNS servers started to register
> EventID 4521, error 9002. Description: The DNS server encountered error
> 9002
> attempting to load zone . from Active Directory. The DNS server will
> attempt
> to load this zone again on the next timeout cycle.
>
> Updates to the three zones I have seem to be showing up on both servers so
> I
> don't know which zone isn't loading. I don't think the error message knows
> either, it's probably suppost to display the zone name in the description.

Danny,

Thanks for the suggestion. I checked and I don't have a "." zone in my
Forward Lookup Zones. I also checked with ADSI Edit.

- Ron



"Danny Sanders" wrote:

> The DNS server encountered error 9002
> > attempting to load zone . from Active Directory. The DNS server will
> > attempt
> > to load this zone again on the next timeout cycle.
>
>
> It may be talking about the "." (dot) forward lookup zone that is created by
> default and in most DNS setups is deleted to prevent the DNS server from
> thinking it's a root server and allowing forwarders to be set up.
>
>
> See How to Remove the Root DNS Zone in this article:
> http://support.microsoft.com/kb/323380/en-us
>
> hth
> DDS
>

Hello Ron,

Thank you for using newsgroup!

This problem may be caused by the corrupt DNS zone. I recommend you
re-create the DNS zone, please refer to the following KB to perform this:

How to reinstall a dynamic DNS Active Directory-integrated zone
http://support.microsoft.com/kb/294328/en-us

If this method can't solve the problem, please let me know the following
information so that I'm able to understand your situation more clearly:

1. What is the OS version of the DNS Server.
2. Save Sysem event log, Dns event log, Application event log to .evt file
and post these files in newsgroup.

Thanks & Regards,

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Mike,

Thanks. It took a couple of days to carefully move both servers to
non-AD-integrated DNS and then back to integrated AD, but that fixed the
problem. Fortunately I didn't need to delete the text-based zone info as the
KB article directed so I didn't lose any important DNS records (MX, CNAME,
etc.).

Regards,

Ron

"Mike Luo [MSFT]" wrote:

> Hello Ron,
>
> Thank you for using newsgroup!
>
> This problem may be caused by the corrupt DNS zone. I recommend you
> re-create the DNS zone, please refer to the following KB to perform this:
>
> How to reinstall a dynamic DNS Active Directory-integrated zone
> http://support.microsoft.com/kb/294328/en-us
>
> If this method can't solve the problem, please let me know the following
> information so that I'm able to understand your situation more clearly:
>
> 1. What is the OS version of the DNS Server.
> 2. Save Sysem event log, Dns event log, Application event log to .evt file
> and post these files in newsgroup.
>
> Thanks & Regards,
>
> Mike Luo
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hello Ron ,

Thank you for the confirm. Glad to know that everyting is OK now. It is my
pleasure to be of assistance.

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

The problem re-appeared after the DNS servers rebooted from installing the
latest WSUS updates (KB925902). This was the first time the DNS service was
restarted since I fixed the problem. By using DNSCMD, I found out that the .
zone is the DNS cache and that it was AD-integrated (/ZoneInfo). Things I
tried that didn't work: clearing the cache and deleting the RootDNS object
from AD.

What finally worked: changing the "Load zone data on startup" from AD +
registry to just registry. Now DNSCMD /ZoneInfo tells me that the cache is no
longer AD-integrated but file based which will probably be okay with me.

Hi Ron,

Great experience sharing! Hope to hear from you again in newsgroup.

Have a nice day!

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

I am seeing the same DNS Event ID 4521 problem. In my case the AD-integrated
zone in question is at a customer who has their external (real) domain in use
as the AD domain (Pre-existing setup - I didn't do it!). All was well enough
before SP2. I am a bit concerned about the recommendation to change from
"from active directory and registry" to "registry". What exactly is this
going to do? What will I lose if I make this change? The environment has 2
AD servers and workstations that of course are set to register in DNS.

Hi
I have Event ID 4521 after SP2 upgrade one of my servers. I did not install
it on others.
The DNS server encountered error 9002 attempting to load zone . from Active
Directory. The DNS server will attempt to load this zone again on the next
timeout cycle. This can be caused by high Active Directory load and may be a
transient condition.

Heeeeeeeeeeeeeeeeeeeelp!
Thanks
Kevin

"Jonathan Huber" <JonathanHuber@discussions.microsoft.com> wrote in message
news:89427F37-62B3-43EA-88B3-E92B5B49DBC5@microsoft.com...
>I am seeing the same DNS Event ID 4521 problem. In my case the
>AD-integrated
> zone in question is at a customer who has their external (real) domain in
> use
> as the AD domain (Pre-existing setup - I didn't do it!). All was well
> enough
> before SP2. I am a bit concerned about the recommendation to change from
> "from active directory and registry" to "registry". What exactly is this
> going to do? What will I lose if I make this change? The environment has
> 2
> AD servers and workstations that of course are set to register in DNS.

[fireater]

Originally Posted by Ron

The problem re-appeared after the DNS servers rebooted from installing the
latest WSUS updates (KB925902). This was the first time the DNS service was
restarted since I fixed the problem. By using DNSCMD, I found out that the .
zone is the DNS cache and that it was AD-integrated (/ZoneInfo). Things I
tried that didn't work: clearing the cache and deleting the RootDNS object
from AD.

What finally worked: changing the "Load zone data on startup" from AD +
registry to just registry. Now DNSCMD /ZoneInfo tells me that the cache is no
longer AD-integrated but file based which will probably be okay with me.

I used the following the my two AD DNS servers at my Domain Core.
DNSCMD /ZoneInfo . <----- The root (not needed for AD)
I saw it was indeed DS intergrated. So I did the following
DNSCMD /Config . /Bootmethod
This makes only that Zone a file load on boot. The below is from MS Technet.

/bootmethod[ 0|1|2|3]
Determines the source from which the DNS server gets its configuration information. ValueDescription0No source.1Loads from the BIND file that is located in the DNS directory; by default, %systemroot%\System32\DNS..2Loads from the registry.3Loads from Active Directory and the registry. This is the default setting.

Did this on both of the server having the problem and it is now fixed. No more events.

Hope that helps.

Any help with this? Anyone? Is it safe to make the recommended change from
"from active directory and registry" to "registry" in my scenario where the
real external domain and internal AD domain are the same?

"Jonathan Huber" wrote:

> I am seeing the same DNS Event ID 4521 problem. In my case the AD-integrated
> zone in question is at a customer who has their external (real) domain in use
> as the AD domain (Pre-existing setup - I didn't do it!). All was well enough
> before SP2. I am a bit concerned about the recommendation to change from
> "from active directory and registry" to "registry". What exactly is this
> going to do? What will I lose if I make this change? The environment has 2
> AD servers and workstations that of course are set to register in DNS.

Hi
I exchecuted:
dnscmd /config /BootMethod
and it works. I have not errors in log now
Thanks
Kevin
>
> Ron;2730340 Wrote:
>> The problem re-appeared after the DNS servers rebooted from installing
>> the
>> latest WSUS updates (KB925902). This was the first time the DNS service
>> was
>> restarted since I fixed the problem. By using DNSCMD, I found out that
>> the .
>> zone is the DNS cache and that it was AD-integrated (/ZoneInfo). Things
>> I
>> tried that didn't work: clearing the cache and deleting the RootDNS
>> object
>> from AD.
>>
>> What finally worked: changing the "Load zone data on startup" from AD
>> +
>> registry to just registry. Now DNSCMD /ZoneInfo tells me that the cache
>> is no
>> longer AD-integrated but file based which will probably be okay with
>> me.
>
> I used the following the my two AD DNS servers at my Domain Core.
> DNSCMD /ZoneInfo . <----- The root (not needed for AD)
> I saw it was indeed DS intergrated. So I did the following
> DNSCMD /Config . /Bootmethod
> This makes only that Zone a file load on boot. The below is from MS
> Technet.
>
> /bootmethod[ 0|1|2|3]
> Determines the source from which the DNS server gets its configuration
> information. ValueDescription0No source.1Loads from the BIND file that
> is located in the DNS directory; by default,
> %systemroot%\System32\DNS..2Loads from the registry.3Loads from Active
> Directory and the registry. This is the default setting.
>
> Did this on both of the server having the problem and it is now fixed.
> No more events.
>
> Hope that helps.
>
>
> --
> fireater
> ------------------------------------------------------------------------
> fireater's Profile: http://forums.techarena.in/members/14440.htm
> View this thread: EventID 4521 warning after SP2 upgrade
>
> http://forums.techarena.in
>

On May 7, 1:57 pm, "Kevin" <k...@yahoo.com> wrote:
> Hi
> I executed:
> dnscmd /config /BootMethod
> and it works. I have not errors in log now

Thanks, Kevin. This really works!

BTW, the output of the command says:
Registry property BootMethod successfully reset.

-- rpr. /Robert Premuz/

The error wasn't shown after i run the command

But when i reboot the server, the error still appear again

Does anyone meet it like me ??

"rpremuz@yahoo.com" wrote:

> On May 7, 1:57 pm, "Kevin" <k...@yahoo.com> wrote:
> > Hi
> > I executed:
> > dnscmd /config /BootMethod
> > and it works. I have not errors in log now
>
> Thanks, Kevin. This really works!
>
> BTW, the output of the command says:
> Registry property BootMethod successfully reset.
>
> -- rpr. /Robert Premuz/
>
>