Event 4512 Error 9906
Contents |
Chris (Microsoft) Technical Consultant/SI GROUP
Error 9906 Dns Server 2012
SPONSORED BY MICROSOFT TECHNOLOGY IN THIS DISCUSSION Join the Community! the dns server was unable to create the built-in directory partition 9906 Creating your account only takes a few minutes. Join Now Hi all, We are receiving DNS Error 4512: "Ereignistyp: Warnung Ereignisquelle: DNS Ereigniskategorie: Keine Ereignis-ID: 4512 Datum: 03.08.2010 Zeit: 03:27:55 Benutzer: Nicht zutreffend Computer: Titan2010.shp2007.local Beschreibung: Der DNS-Server konnte keine integrierte Verzeichnispartition "ForestDnsZones.shp2007.local" erstellen. Fehler: 9906. Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp. Daten: 0000: b2 26 00 00 ²&.. "
This event ocures since we extended our domain (one W2000 DC) with another DC (W2008 R2). I haven't found a solution yet, also google has not provided an answer yet. Does anyone knows how to get rid of that error? Thanks Sven Reply Subscribe View Best Answer RELATED TOPICS: Windows 2008 R2 KB3145126 KILLED DNS DNS issues with Windows 2008 R2 Windows 2008 R2 SQLWriter Error 5 Replies Habanero OP Helpful Post CharlieB Aug 12, 2010 at 8:35 UTC This might help: http://technet.microsoft.com/en-us/library/cc735663(WS.10).aspx 0 Habanero OP Helpful Post Jose Franco Aug 12, 2010 at 8:59 UTC Información Tech is an IT service provider. Hello, The DNS server was unable to create the built-in directory partition. http://technet.microsoft.com/en-us/library/dd393046(WS.10).aspx http://technet.microsoft.com/en-us/library/cc735663(WS.10).aspx (CharlieB posted it, also) 0 Pimiento OP SvenBade Aug 12, 2010 at 9:15 UTC Hi folks! Thanks for the resonse. I clicked on "Create Default Application Directory Partitions".Login
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login https://www.experts-exchange.com/questions/27270141/AD-DNS-issues-after-adding-Windows-2008R2-DC-to-existing-Windows-2000-AD.html Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > AD, DNS issues after adding Windows 2008R2 DC to existing Windows 2000 AD Want to Advertise Here? Solved AD, DNS issues after adding Windows 2008R2 DC to existing Windows 2000 AD Posted on 2011-08-23 Active Directory Windows Server 2008 DNS 2 Verified Solutions 15 Comments 2,500 Views Last Modified: 2012-05-11 I am in the process of migrating an existing domain error 9906 from a Windows 2000 Domain Controller with Exchange 2003 to Windows 2008R2 with Exchange 2010. I have configured a new Windows 2008R2 Hyper-V Guest onto the network using a static IP, with DNS pointing at the existing 2000 DC and joined the domain. I ran adprep32 /forestprep and /domainprep /gpprep on the 2000 DC (from the 2008R2 media /support folder). I then ran dcpromo on the 2008R2 machine which appeared to run successfully, apart from a message at event 4512 error the end of the process "A delegation for this DNS Server will not be created because the authoritative parent zone cannot be found or it does not support dynamic updates" which I ignored, as a quick search said the message was fine in a single domain. Now I have the following issues: Logging on to the 2008R2 machine using a domain account is very slow. DNS resolution doesn't seem to work correctly - pinging the Windows 2000 DC by name doesn't return the correct IP address (just to confuse things, this site has a AD domain name set the same as their external DNS name, i.e. xyz.com). So pinging windows2000dc.xyz.com returns the external IP address of the web server for the domain rather than the internal IP address. Other 2008R2 member servers ping this internal machine by name just fine. NSLOOKUP returns the prompt "Default Server: UnKnown, Address: ::1" and doesn't resolve internal machine names correctly, but if I enter "server 192.9.205.10" (my 2000DC internal server IP) it resolves fine. Is the strange [inherited] internal IP range causing a problem here? The DNS server address of in the LAN card settings is set to the IP of the 2000DC server, but it's like the system is completely ignoring this. Event Viewer shows several events on the 2008 machine: DNS Server event 4512 "The DNS server was unable to create the built-in directory partition ForestDnsZones.xyz.