Cannot create Child Domain, DNS server not working correctly

Hello. I have just recently made a Windows 2000 stand-alone server into a Domain Controller. Along with adding active directory I had to implement DNS with it. Everything looks fine and is able to send and receive files across the network, however...  I am trying to create a network map that is very clean and tidy by dividing the plants across the state into seperate Domains. The first Domain I need to make will be based in the same LAN that the Primary DC is located on a separate file server. My problem is when I try to run dcpromo and make the File Server into a Child Domain I get an error when I try to establish the DNS server I created as the primary DNS server for the Child Domain.
ERROR: "An Active Directory domain controller for the domain suncoast.local could not be contacted."
"Ensure that the DNS domain name is typed correctly."
Part of the details say, "The DNS SRV records required to locate a domain controller on the domain are not registered with the DNS server."

Additionally, when we ran dcdiag to see what happened, this is what came up.
"SUNCOAST1's server GUID DNS name could not be resolved to an IP address. Although the GUID DNS name 667a6853-984a-46ee-b0c3-f73b70a33e36._msdcs_.suncoast.local couldn't be resolved, the server name suncoast1.suncoast.local resolved to IP address *.*.*.* and was pingable.

Now our server's computer name is suncoast1. Our DC's domain name is suncoast1.suncoast.local.

Any help with this issue would be greatly appreciated. Thanks.
coilbrazeAsked:
Who is Participating?
 
Jay_Jay70Commented:
Hi coilbraze,

first of all, change the server name to something other than that of the same name of the domain,

second make sure you can ping the root DC by name and IP, how have you configured DNS on the soon to be child DC? did you add the root DC as a forwarder and then let it run that way?
0
 
coilbrazeAuthor Commented:
I can ping the DC by name and IP. DNS is not yet set up on the soon to be child DC. But I have found part of the solution. To get DNS to work correctly on the root DC I had to set itself as it's primary DNS, then all the workstations with the DC as the DNS finally responded correctly in nslookup. What it ended up being I believe was that I had to cycle netlogon service for my SRV records to show up. You see, before I cycled netlogon, I had no _msdcs folder in DNS, or any automatically generated DNS folders for that matter. Once I got that working I renamed the server as you said, but then the child domain had problems with the RPC server. In which case I had to turn on trust delegations between the two for them to work appropriately. THEN, I went to make it a child domain, and it told me I need to run adprep utility to prepare the Windows 2000 server forest and the Windows 2003 server domain before I can make the server a domain. Had to learn a lot of stuff to figure this all out and I still feel like it was luck hehe. Thank you Jay_Jay70, changing the server name seems to have gotten it and us less confused.
0
 
Jay_Jay70Commented:
well done my friend
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
coilbrazeAuthor Commented:
GAH. When I ran DCPROMO and tried to add the child domain to our windows 2000 DC, it told me I needed to run adprep utlility to prepare the Forest and the Domain. In doing this it caused the 2003 server to disjoin from the domain, in lieu of which we decided to change the name of the server in order to be compatable with the infrastructure we were planning on. Once the server restarted I have come across yet more errors.

I have since configured and reconfigured DNS about 16 times, it is working correctly as far as I know, but now I am receiving the error:
"the wizard cannot gain access to the list of domains in the forest."
"The condition may be caused by a DNS lookup problem."
The error is: RPC server unavailable.

Now last time I got this error I was able to bypass it by adding a trust delegation between the soon to be child domain and the windows 2000 DC. This seemed to fix it, until I rebooted, tried to add the same trust delegation, and now the error won't go away. Any help? thanks.
0
 
Jay_Jay70Commented:
0
 
coilbrazeAuthor Commented:
Ok, so I resolved the problem stated earlier, not sure how, it was last week, sorry. NOW, the problem I am having is this. We have successfully run adprep, and added the 2003 server as a child domain. However, the 2003 child domain is not showing up to the windows 2000 DC. We made the 2003 server a DC in AD, but the child domain isn't showing up in the network browser, and anytime we try to connect to the child domain, it says it can't find it. Does the 2003 child domain need to have some kind of security policy added? or be a member of some group like Domain Admins or something? There are so many possible user policy restrictions, that I don't know where to look, or if even that's what the problem is. Any help is appreciated again, thanks.
0
 
Jay_Jay70Commented:
does the the child domains DC turn up under AD sites and Services?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.