Dns 4000 Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: DNS Error ID 4000 on a domain controller Windows Server > Network Infrastructure Servers Question 0 Sign dns error 4000 active directory in to vote Hi all, I had an AD with 2 DC, let's say
Dns Error 4000 4004
DC1 and DC2, DC1 was the FSMO holder. DC1 have crushed and can't be restored so I've seized the FSMO roles
Dns Error 4015
to the DC2 and have cleaned the metadata with "ntdsutil metadata cleanup" no errors have arisen during theese tasks. I've rebooted DC2 and have theese problems: DNS Error ID 4000 "The DNS server was unable
Dns Server Error 4000
to open Active Directory. 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." If I go to my dns manager I can't se the AD integrated zone Moved by Rick TanModerator Friday, May 20, 2011 3:19 the dns server was unable to open active directory 2008 r2 AM (From:General) Wednesday, May 18, 2011 8:22 AM Reply | Quote All replies 0 Sign in to vote Try resolution mentioned here:http://technet.microsoft.com/en-us/library/dd349683(v=WS.10).aspx Please make sure that the DC is not yet pointing to the old DC as a DNS server and that it is pointing to itself as primary DNS server. Do you have missing zones? If yes, which one of them? This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Wednesday, May 18, 2011 8:24 AM Reply | Quote 0 Sign in to vote Have just tryed that solution, it obvious not worked... DC2 is now pointing to itself as DNS server I'm missing all AD integrated zone both forward and reverse lookup Wednesday, May 18, 2011 8:36 AM Reply | Quote 0 Sign in to vote Okay, create an AD integrated zone for your domain and then run ipconfig /registerdns and restart netlogon. This posting is provided "AS IS" with
(66)Linux BSD (9)Musings (15)Networks (13)PowerShell (81)TV (14)Virtualization (58)Windows (171)WordPress (8)Tagsacl acls active directory android Azure batch file batman casting dfs disks dism dns domain controller encryption esxi event logs exchange2010 git group policy heroes hp hyper-v ipv6 nat networking nslookup openvpn powercli powershell the dns server was unable to open active directory 2012 regexp reports server2008 server2012 servercore solarwinds ssh string manipulation vcenter vmware vsphere windows dns error 4007 windows7 windows8 wmi workshopPLUSRecent Posts Use PowerShell to get a list of GPOs without Authenticated Users in the delegation netdom resetpwd /server:
only takes a few minutes. Join Now All: I am currently having some flaky issues with one of my Domain Controllers (Windows Server 2003). In my environment, I currently have two DC's. As of right now, I am seeing errors on the 2003 DC, in the fashion that it cannot https://community.spiceworks.com/topic/296657-primary-dns-server-unable-to-open-active-directory contact the DNS Server (Which is itself...). I am also receiving multiple errors in the Event Viewer (Event http://www.eventid.net/display.asp?eventid=4000&eventno=334&source=DNS&phase=1 ID 4000), stating that the DNS server was unable to open Active Directory. I have also noticed that all forward, and reverse zones are not available on this DC, as they are AD integrated. Relating to this issue, however still weird, is the fact that I have two shares on the local drive of this machine. These shares are not reachable by FQDN, but they are reachable by IP. I have other dns error shares on other PC's, that I can resolve no problem by FQDN (Remember, I have two DC's in my environment)? So I am curious to why the shares on the server having issues are not accessible by fqdn? Shouldnt DC #2 pickup this fqdn of the share? Any help would be appreciated! Reply Subscribe View Best Answer RELATED TOPICS: The DNS server was unable to open Active Directory. My DNS Server unable to open Active Directory DNS Server Issues   This topic was created during version 6.2. The dns error 4000 latest version is 7.5.00093. 1 2 Next ► 26 Replies Habanero OP Randy1699 Jan 29, 2013 at 4:58 UTC 1) IS the DNS ip address for this flaky machine the ip address that it uses for DNS? In other words, it points to itself for DNS. 2) Reload the Zone 0 Sonora OP IT_CHAD Jan 29, 2013 at 5:17 UTC Randy: 1) Yes, the flaky server is using itself's as it's DNS 2) I am not able to reload the zones? I completed a restart of the DNS, but after the restart, I receive numerous Event 4007 in the log. These are noting that the DNS was unable to open my zones? Any ideas? 0 Habanero OP Randy1699 Jan 29, 2013 at 5:33 UTC Delete the subnets, forwarders, etc and then recreate them. What OS is the other DNS? 0 Habanero OP Randy1699 Jan 29, 2013 at 5:39 UTC Run dcdiag /test:DNS and ipconfig /all on the DNS server having the problems and post here. 0 Sonora OP IT_CHAD Jan 29, 2013 at 5:49 UTC Would you recreate the zones as secondary( Copy them from other DNS)? 0 Sonora OP IT_CHAD Jan 29, 2013 at 6:01 UTC Attached is the output of the DCDIAG /DNSALL.... DNS_Testing.txt (4.77 KB) 0 Sonora OP IT_CHAD Jan 29, 2013 at 6:02 UTC Here is the output of the IPCONFIG /ALL... 0 Habanero OP Randy1699 Jan 29, 2013 at 6:36 UTC DsGetDcName returned
Analyzer Sample report Advanced filtering Direct links to www.eventid.net Email notifications Scheduled reporting Free for subscribers EventReader Event Viewer Sample report Custom views/filters Servers list, organized in groups Integration with EventID.Net Consolidated view for all logs Free for subscribers Event ID: 4000 Source: DNS Type: Error Description:The DNS server was unable to open Active Directory.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. Data: 0000: f5 25 00 00 5 Comments for event id 4000 from source DNS Source: fwdrv Type: Error Description:The description for Event ID ( 4000 ) in Source ( fwdrv ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: