secondary DNS server 2003

Posted on 2004-11-14
Medium Priority
Last Modified: 2010-03-18
I am settign up a secondary dc on 2003 server.  The primary dc is on 2000 server.  Each dc is behind NAT(linksys routers) on a separate public ip.

2000 server dc
link sys port 53 forward to lan ip
lan ip

2003 server dc
link sys port 53 forward to lan ip
lan ip

When I try to join the new dc to the existing domain I get the following error

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

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

The following domain controllers were identified by the query:


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.

For information about correcting this problem, click Help.

I setup DNS on the new server, ns2.joeker.org, as a secondary DNS for the zone and it successfully transports the dns info from ns1.joeker.org
But there is a host record that shows the lan ip of ns1.  I delete t but it keeps recreating itself.


Question by:joeker
  • 2
LVL 104

Expert Comment

ID: 12583145
As the new machine is Windows 2003, have you run forest prep and domain prep to turn the domain in a Windows 2003 mixed domain? You cannot put a Windows 2003 machine in to a Windows 2000 domain until you do - although a Windows 2003 server will work in a Windows 2000 domain as a member server.

If you are putting this server in as a domain controller, setup DNS, but don't configure it. Then DCPROMO the server in. If this doesn't create the AD integrated zone, create it yourself. Don't replicate anything - the AD will do that for you.
The key thing is to let AD do as much as possible. Trying to do anything else yourself will often cause problems.


Author Comment

ID: 12734176
Sorry for the late reply.  
I ran forest and domain prep on the 2000 server when I originally set it up.  I havn't been able to get the 2003 server to join the 2000 server domain.  Maybe I should call the question "2003 server joining 2000 server domain".

LVL 104

Accepted Solution

Sembee earned 600 total points
ID: 12741126
If you are adding a 2003 machine as a domain controller then you need to run 2003 forest prep and domain prep. The 2000 forest prep and domain prep is not enough.


Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you one of those front-line IT Service Desk staff fielding calls, replying to emails, all-the-while working to resolve end-user technological nightmares? I am! That's why I have put together this brief overview of tools and techniques I use in o…
An article on effective troubleshooting
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
The Relationships Diagram is a good way to get an overall view of what a database is keeping track of. It is also where relationships are defined. A relationship specifies how two tables connect to each other. As you build tables in Microsoft Ac…

579 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question