Dns Error 9906
Contents |
Guest after promoting first w2k8 dc in w2k domain I've noticed the following errors in DNS log: The DNS server was unable transfer dns from 2000 to 2008 to create the built-in directory partition ForestDnsZones.heathmill.com. The error was 9906. The DNS migrate dns from 2000 to 2008 r2 server was unable to create the built-in directory partition DomainDnsZones.heathmill.com. The error was 9906. with the following action suggested:
Error 9906 Dns Server 2012
http://technet.microsoft.com/en-us/library/cc735663.aspx how safe is it to "create a forest-wide and domain-wide DNS directory partition" and will this override anything in the old DCs? it is suggesting to "Create Default Application Directory
Error 9906 Itunes
Partitions" and those were intriduced in w2k3 as far as I know so should be pretty safe to carry out? Gueorgui Dimov, Aug 15, 2008 #1 Advertisements Avinash Guest The error 9906 really means as follows: net helpmsg 9906 The application directory partition operation failed. The domain controller hold ing the domain naming master role is down or unable to service the domain naming master fsmo role could not be reached the request or is not running Windows Server 2003. Ensure the FSMO role holder is up and running. Also, you can try Log on as Enterprise Admin and do the same. As far as creating the forest-wide and domain-wide DNS directory partition is concerned take help of the Microsoft Technical Support to ensure nothing is going to overwritten. Regards, Avinash Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. "Gueorgui Dimov" wrote: > after promoting first w2k8 dc in w2k domain I've noticed the following > errors in DNS log: > The DNS server was unable to create the built-in directory partition > ForestDnsZones.heathmill.com. The error was 9906. > The DNS server was unable to create the built-in directory partition > DomainDnsZones.heathmill.com. The error was 9906. > with the following action suggested: > http://technet.microsoft.com/en-us/library/cc735663.aspx > > how safe is it to "create a forest-wide and domain-wide DNS directory > partition" and will this override anything in the old DCs? > it is suggesting to "Create Default Application Directory Partitions" and > those were intriduced in w2k3 as far as I kno
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: 2000 DNS > 2008 DNS Windows Server > Migration Question 0 Sign in to vote Hi,I've just promoted my new 2008 servers, everything seems ok and now was wondering how easy it is to migrate the DNS from my 2000 dc's to the 2008? Has anyone done this before and could give me an http://www.winvistatips.com/threads/dns-server-was-unable-to-create-the-built-in-directory-partition.735860/ idea? Phil Tuesday, June 17, 2008 2:45 PM Reply | Quote Answers 0 Sign in to vote Hi, When you create AD integrated DNS on DC, the DC needs to create application partition and will contact domain name master to update the corresponding information. The error was 9906 indicates domain controller holding the https://social.technet.microsoft.com/Forums/windowsserver/en-US/5bb40dcf-4ddd-4d4a-891e-48b45dbef709/2000-dns-2008-dns?forum=winserverMigration domain naming master role is down or unable to service the request or is not running Windows Server 2003. So, I suspect the problem is in regard to domain name master. I'd suggest you transfer domain name master role to Windows server 2008 DC and test the result. I list some useful articles that would be helpful for your reference: How to view and transfer FSMO roles in the graphical user interface http://support.microsoft.com/kb/255690 Initial synchronization requirements for Windows 2000 Server and Windows Server 2003 operations master role holders http://support.microsoft.com/kb/305476/en-us Hope this helps. Marked as answer by Morgan Che [MSFT]Moderator Monday, June 30, 2008 7:49 AM Friday, June 27, 2008 8:41 AM Reply | Quote Moderator All replies 0 Sign in to vote Assuming you don't have any non-Windows or pre-Windows 2000 DNS Servers:Since you've promoted your Windows Server 2008 servers (to Domain Controllers I assume) you can use Active Directory Integrated DNS Zones. If you haven't done so alre
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 https://www.experts-exchange.com/questions/27270141/AD-DNS-issues-after-adding-Windows-2008R2-DC-to-existing-Windows-2000-AD.html a Full Time Job Ways to Get Help Expand Search Submit Close Search Login 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 error 9906 AD Posted on 2011-08-23 Active Directory Windows Server 2008 DNS 2 Verified Solutions 15 Comments 2,492 Views Last Modified: 2012-05-11 I am in the process of migrating an existing domain 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 dns from 2000 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 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 "