Connecting to a Domain Controller Failure

Hello Experts,

Hope you are all  having a good day :-)

I setup a Windows 2003 Standard Edition Server for a test lab.
Machine Name: Corlocqa1
Domain Name: corkloc.nai.org
This is on a private network
I installed Active directory and it all seems to be fine. I then add a machine to active directory.
However from the client machine when i tried to join the domain corkloc.nai.org i got the following error.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain corlocqa1.corloc.nai.org:

The error was: "DNS server failure."
(error code 0x0000232A RCODE_SERVER_FAILURE)

The query was for the SRV record for _ldap._tcp.dc._msdcs.corlocqa1.corloc.nai.org

Common causes of this error include the following:

- The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with following IP addresses:

212.23.8.1
192.168.1.17
159.134.237.6
159.134.248.17

- One or more of the following zones contains incorrect delegation:

corlocqa1.corloc.nai.org
corloc.nai.org
nai.org
org
. (the root zone)


Can you please advise as to where i have gone wrong. This is my first shot at setting up a Domain Controller.

Many thanks in Advance
Angela
ANGELA11Asked:
Who is Participating?
 
f_umarConnect With a Mentor Commented:
run DCPROMO to remove active directory then run it again to add it
DCPROMO will offer to configure DNS for you, say yes and go to lunch
Once you finish lunch the DCPROMO should be done and ready for rebooting, then you'll have a working set of zone files
Active Directory zone file, you'll never get it right making it by hand
0
 
ANGELA11Author Commented:
Thank you F umar i will try that right away and report back :-)
0
 
NJComputerNetworksCommented:
Another point...  

After you remove active directory, and before you run DCPROMO again....do this

Go into TCP/IP properties on the server.  Make sure that you set DNS to point to 127.0.0.1 (and no other address)

Now run DCPROMO on the server and choose to instal the DNS service locally (this is the default option)

0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
NJComputerNetworksCommented:
I just reread your post, you say that AD is running fine on the server.  This can only be true if the DC / DNS server is pointed properly. Maybe the only problem is that you client isn't pointed to your Internal Windows 2003 DNS server.

All clients and members of an Active directory domain must use the internal Windows 2003 DNS server.  This is because DNs is required to properly "talk" to the domain.

Therefore, you must point your client to the IP address of the DNS Windows 2003 DNS server.  

Server DC  NAme: Server1
IP:  10.10.10.5
Subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS: 127.0.0.1 or 10.10.10.5

Client NAme:  Client1
IP: 10.10.10.50
Subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS: 10.10.10.5  <-- must be pointed to internal Windows 2003 DNS server and no other DNS servers should be listed.
0
 
f_umarCommented:
if u r using dhcp for ip configuration then configure scope options 006 for DNS servers and authorize it for the domain.

0
 
f_umarCommented:
i think he has configured correct dns so why he can be able to resolve "corkloc.nai.org"
u should go with dcpromo
0
 
NJComputerNetworksCommented:
Another thing:  When you name your windows 2003 domain name, pick a name that is not registered on the internet...  for example company.local or company-int.local or company.inside or company.int

If you name your Windows 2003 domain that exact same name as your registered internet domain name, you will have problems resolving your internet web pages from inside your network.  (This problem can be resolved by manually creating records for your external web sites on your local DNs servers...but its a pain)
0
 
ANGELA11Author Commented:
Hi Folks,

While running dcpromo at the DNS Registratio Diagnostics (My DNS on server is 127.0.0.1)
I got the following error:

Diagnostic Results
The registration diagnostic has been run 3 times.

The wizard could not determine the name and address of the DNS server with which this domain controller will be registered.

For more information, including steps to correct this problem, see Help.

Details
The SOA query for _ldap._tcp.dc._msdcs.corkloc.nai.org to find the primary DNS server returned:
 DNS server failure.
(error code 0x0000232A "RCODE_SERVER_FAILURE")

Any ideass ???
0
 
f_umarCommented:
it seems your computer is pointing to your isp dns, point your dns to internal ip not 127.0.0.1 but the static ip which u configured like 192.168.100.1 also check the binding order.
0
 
f_umarCommented:
When you run dcpromo on the first domain controller in a new domain it gives you the option of making it a DNS server as well, make sure you read through the wizard carefully and look for that option. There has to be atleast one local DNS server in the domain.
0
All Courses

From novice to tech pro — start learning today.