My problem is one that mystifies me. After I set up Server 2003 to be a Domain Controller all of my problems start. Once the setup wizard finishes, the machine reboots and gets back into windows, only it takes 15-20 minutes for it to get past the Preparing Network Connections part of it. Now once I can login I go to add users to my domain it telles me that the domain does not exist or could not be contacted. I can see it in My Network Places and browse shared folders but I cant connect to it. Also, I am trying to add 3 XP Pro machines to this domain and this is the error I continue to get if I type in the full domain of home.server.local:

DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain home.server.local:

The query was for the SRV record for _ldap._tcp.dc._msdcs.home.server.local

The following domain controllers were identified by the query:

server.home.server.local

Common causes of this error include:

- Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or are not running.

This is the error I get if using the NETBIOS name of HOME:

The domain name HOME might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

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

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.HOME

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

HOME
. (the root zone)

I dont know whats happening with this. I have set up a domain 5 times already with different names and the same errors each tim. I'm on the verge of giving up.

Questions:
1. Did you upgrade a DC for an existing Windows 2000 domain?
2. What are you using for DNS?

"How many squirrels had to die to make you look fly?!"

Making the same error repeatedly doesn't get you closer to a solution.

Clearly your issue is DNS for your post.

Does the server point to itself in its tcp/ip dns properties? In other words create a A and PTR record listing the server name and ip address.

There isn't enough info in your post but this can be a result of tcp/ip dns properties pointing to a ISP as dns server not your server as dns server when you run thru dcpromo.

DNS is vital to the domain controller. Might want to tell use the dns settings prior to running dcpromo.

Give a person a fish you feed them for a day.
Ask a person to internet search and they learn a skill for a lifetime.

Response 1
Ok, I did not upgrade a server 2000 domain, this is a fresh install. Im using the server for local DNS and I have it forwarded to my ISP for internet.
Response 2
Well, Im not trying to make the errors appear, they just do. If my problem were DNS then I wouldnt be able to use it for my other computers to resolve names, correct? I believe something is wrong with the way dcpromo is setting up my active directory as half of the time when I try to configure it I keep on getting an error message telling me that the domain does not exist or could not be contacted. Now this particular install disk is one I have used before and have had no problems with. Also, DNS on the server is set to where it uses itself for local name resolution and my ISP for internet

"If my problem were DNS then I wouldnt be able to use it for my other computers to resolve names, correct?"

Not correct. If the records are missing, resources missing those records will not work. It's that simple.

"Also, DNS on the server is set to where it uses itself for local name resolution and my ISP for internet"

Say exactly how you did this. We can't know if you did it right until you say how you did it.

If DCPromo is in fact malfunctioning and behaving as it is supposed to, then there's no way we can help you, right?

"How many squirrels had to die to make you look fly?!"

when i set up the dns server it opened up my TCP/IP properties and i set it to use a static IP from my router and then i set it to use itself for dns, i closed and saved that. then i went into the dns management and got into the properties where i set forwarders to my ISP for internet, same thing I did the last time I set up a domain. as far as I know, the DNS for local name resolution and internet is set up right.

Where these things done before you DCPromo'ed the box?

Also, did you manually setup the DNS server, or did you let DCPromo do it for you?

"How many squirrels had to die to make you look fly?!"

Also, are your XP clients configured to use the server as a DNS server?

"How many squirrels had to die to make you look fly?!"

ok, yes i had dns set up first, yes it was setup manually, and yes all 3 are set up to use the server for dns

"server.home.server.local" and "One or more of the following zones do not include delegation to its child zone"

I think this is where the problem is. I don't believe home could resolve to a netbios name. Its like you have made a subdomain in dns when one doesn't exist in AD.

Mahybe this would help?
http://support.microsoft.com/kb/296...

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

I would recommend the following...

1. Tear down the domain you have.
2. Remove DNS services from the server.
3. Repromote the domain controller.
4. Allow DCPromo to setup DNS on your server.

"How many squirrels had to die to make you look fly?!"

Alright, I'll try that when i get off of work today. Thanks for all the help. I'll probably have another post for you to look at about 6:30 CST and let you know what worked and failed.

and try just using home.local for domain name.

Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

i dont think you can start off that deep of a domain name

Why can't you?

Please help survivors of Hurricane Katrina!

www.redcross.org