secondary DNS server 2003

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

The query was for the SRV record for

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,, as a secondary DNS for the zone and it successfully transports the dns info from
But there is a host record that shows the lan ip of ns1.  I delete t but it keeps recreating itself.


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.

joekerAuthor Commented:
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".

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.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

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.