Windows 2000 DNS Question

When you have the new server setup (before DCPROMO) - install DNS.
Configure the new Forward Lookup Zone for your domain on this server.
Setup Forwarding to the old DNS server.
Point the server to itself only.
Make sure it gets registered in DNS.
Create another Forward Lookup zone (secondary) that corresponds to your new domain - do this on the company1.com DNS server.
Setup DNS on the new domain to do zone transfers to the old DNS server zone.

This should do it.

Carry on with your DCPROMO.

These's links may help you in the future
the first link has a video
http://www.microsoft.com/technet/community/events/windows2003srv/tnt1-114.mspx  = video

http://www.petri.co.il/install_and_configure_w2k_dns_server.htm

good luck davy              

Thanks for the feedback!

One question: Am I correct in assuming that I don't create a forward/reverse lookup zones on my new server that points to itself, i.e. headquarters.company2.com?

Hello

I followed your steps, and am now getting the following error:

Zone not loaded by DNS Server

The DNS server encountered an error while attempting to load the zone............ ANY IDEAS?

Sorry for the delay.

A few Q's..

What server is giving the errors?

You need to create Forward and Reverse Lookup Zones on the new server that are Authoritative for your new Domain, yes.

Make sure that the server has the correct DNS suffix of headquarters.company2.com, the DNS setting on the NIC points to itself and it is set to register in DNS.

Let's start from the beginning and get one thing at a time working.
1)  Remove the secondary zone you created on the original DNS server.

Now, correct me if I'm wrong but headquarters.company1.com is a child domain to company1.com - where is this root domain?  
If you want headquarters.company2.com, where is company2.com?  Does it exist?

2)  If you create a new Forward Lookup Zone on the new server for headquarters.company2.com and your server has the correct DNS suffix, when you stop and restart the Netlogon service on that server does it register in DNS locally?

Advise.

Hello

headquarters.company1.com [172.24.128.*/255.255.255.128] is the root domain. The dns server [172.24.128.1] resides of the RDC. Company1.com is the name used on the internet.

headquarters.company2.com [172.24.130.*/255.255.255.128] is the new domain. This time the dns server [172.24.130.1] will reside on the DC. Company2 will be the na,e used on the Internet.

Also,

[1] The server that is giving the error is the dns server in headquarters.company1.com

I see, now it's making more sense.

This is why Microsoft doesn't recommend your Active Directory namespace be a registered Domain name....it causes your internal namespace to extend onto the Internet and makes local AD-related activity a little more challenging to contain.

So, the root domain for comany1.com is living where?  I'm not sure what RDC refers to.

Any result from 2) above?

Sorry! I'll start again

As you pointed out Microsoft recommends separating namespace. Therefore, the setup I have is as follows:

I have one AD domain [headquarters.company1.com] that has one primary dns server that resides on the root domain controller. For all dns requests that cannot be resolved internally they are forwarded to our firewall (a sidewinder G2) that runs a split level dns server for resolution. The external namespace is company1.com.

Everything with this set up works great!

The problem I have is that I need to create an additional tree [headquarters.company2.com] because the namespace will be different.

I want to configure the new dns server for headquarters.company2.com so that it has a bi-directional link with the dns server that already exists in headquarters.company1.com, so that I can then run dcpromo and add the new domain controller in as a member of the existing forest.

NOTE: By RDC I meant Root Domain Controller - Top of the tree so to speak.

Eventually, the new server [headquarters.company2.com] will be moved to another location and will reside behind a firewall, however, for the time beginning I have connected it to the existing lan [headquarters.company1.com]

SORRY I FORGOT:

From an internal point of view headquarters.company1.com id the root domain

Hello, thanks for the feedback

I followed the following recommendation by microsoft when setting up the dns naming convention:

http://support.microsoft.com/kb/254680

I can't make it active directory integrated because I haven't run dcpromo. The reason I haven't do that is becasue I need the dns link in first so that i can connect to the existing forest dns server [headquarters.company1.com], and subsequently have the new server made part of the existing AD domain.

Again, sorry for the delay - car repairs and dentist today!

OK...

Gotcha - Can't AD integrate - yet...my bad.

Here's what we can do in the interim to get you working enough to do a DCPROMO then we can tune up your DNS once it's up.

Do this on the new server:

In LMHOSTS (C:\Windows\System32\Drivers\Etc.) enter the name of the server that is hosting headquarters.company1.com and it's IP.
In HOSTS enter the Domain name headquarters.company1.com and give it the IP of the DC.
In HOSTS enter the FQDN of the DC also - servername.headquarters.company1.com.

LMHOSTS.SAM is a template.  Open it in Notepad, make your additions then save it as LMHOSTS (no extension).
HOSTS can be edited the same way - be careful when saving as it might add the extention of .txt if you aren't watching.

Now you should be able to DCPROMO since it can effectively find the other domain and DC by name and IP.

Advise.

Good Morning!

Don't worry about the delay, I really apprecaite the help.

I've followed the steps above, yet when I try and ping by ip or name, I get no repsonse! Any ideas?

ping intiated from: server2.headquarters.company2.com / 172.24.130.1:255.255.255.128
ping destination: server1.headquarters.company1.com / 172.24.128.1:255.255.255.128

How are these two networks connected?  

What are you using for a gateway for the new server?

Can the gateway pass ICMP?


I will be away from the computer for awhile today - again.  Keep asking!

Cheers.

Thank god for that!!! The problem was down to the DNS configuration on the firewall, the routing between the two subnets wasn't working correctly.

Perfect!  I knew it had to be simple.

Glad you're off and running.

I'm all ears!  Well...not ALL ears! :o)