DNS Error 4007

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

On a new, single server domain, the Windows 2003 server shows event 4007
twice when it starts up. The error says

"The DNS server was unable to open zone _msdcs.zonename.local in the Active
Directory from the application directory partition
ForestDnsZones.zonename.local. This DNS server is configured to obtain and
use information from the directory for this zone and is unable to load the
zone without it. Check that the Active Directory is functioning properly and
reload the zone. The event data is the error code."

In the DNS MMC, I see two forward lookup zones: there is the zonename.local
forward lookup zone showing the _msdcs folder grayed out. There is also a
_msdcs.zonename.local forward lookup zone.

Communication and name resolution appear to be working but I don't know
where the error is coming from. Should there be two forward lookup zones as
described? Where to start troubleshooting this? Thanks for any help.

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Hi

This event usually occurs because the AD isn't quite ready when the DNS
server service starts. It's normally not something you need to worry about
provided the event only occurs at boot time. You can also test this by
moving the zone(s) to standard primary non active directory integrated and
see if they occur ... chances are that they won't.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: markreno@online.microsoft.com

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

"jkf1024" <jkf1024@discussions.microsoft.com> wrote in message
news:752B7C64-60FF-42DE-8663-40664409624B@microsoft.com...
> On a new, single server domain, the Windows 2003 server shows event 4007
> twice when it starts up. The error says
>
> "The DNS server was unable to open zone _msdcs.zonename.local in the
> Active
> Directory from the application directory partition
> ForestDnsZones.zonename.local. This DNS server is configured to obtain and
> use information from the directory for this zone and is unable to load the
> zone without it. Check that the Active Directory is functioning properly
> and
> reload the zone. The event data is the error code."
>
> In the DNS MMC, I see two forward lookup zones: there is the
> zonename.local
> forward lookup zone showing the _msdcs folder grayed out. There is also a
> _msdcs.zonename.local forward lookup zone.
>
> Communication and name resolution appear to be working but I don't know
> where the error is coming from. Should there be two forward lookup zones
> as
> described? Where to start troubleshooting this? Thanks for any help.

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

jkf1024 wrote:
> *On a new, single server domain, the Windows 2003 server shows event
> 4007
> twice when it starts up. The error says
>
> "The DNS server was unable to open zone _msdcs.zonename.local in the
> Active
> Directory from the application directory partition
> ForestDnsZones.zonename.local. This DNS server is configured to
> obtain and
> use information from the directory for this zone and is unable to
> load the
> zone without it. Check that the Active Directory is functioning
> properly and
> reload the zone. The event data is the error code."
>
> In the DNS MMC, I see two forward lookup zones: there is the
> zonename.local
> forward lookup zone showing the _msdcs folder grayed out. There is
> also a
> _msdcs.zonename.local forward lookup zone.
>
> Communication and name resolution appear to be working but I don't
> know
> where the error is coming from. Should there be two forward lookup
> zones as
> described? Where to start troubleshooting this? Thanks for any help.
> *

I experienced this same issue on a newly set up windows 2003 AD. I
reloaded the zones multiple times, and I was getting the same 4007
events. I got the events everytime I: started the DNS server service,
not only when I booted the server. I blew out the DNS service under
Add/remove windows components, and added it back in. After I did that,
I did not see another 4007 error. I am still unsure as to why this
problem happened, but it seems to be working now with no problems.



--
joekemp
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message485825.html