Solved

Issue with 2nd DNS Controller Zone

Posted on 2009-05-07
9
261 Views
Last Modified: 2012-05-06
I have a new DC on 2003R2 that I am building to replace existing 2003 DC. I am at the stage of setting up DNS. I want to build the DNS on the new box from scratch instead of pulling over the old existing one. Since I can't create a zone on the new DC with the same Zone name of "OurDomain" that is currently running on the dying DC, I have some questions.

Does the zone have to be the same name as our Domain?  Is there anything I should be aware of by introducing a new DNS zone name? Can I have both running temporarily until finished transfering fsmo roles to the new box?
0
Comment
Question by:MushroomStamp
  • 4
  • 3
  • 2
9 Comments
 
LVL 70

Expert Comment

by:Chris Dent
ID: 24330275

The zone name you create must match your AD Domain, you can't create an arbitrary zone name here, there's no point.

You could change the zone type on the current server to Standard Primary (remove the AD Integrated tick). Then you can have two zones of the same name (one on each server).

May I ask why you want to drop the current zone?

Chris
0
 
LVL 57

Expert Comment

by:Mike Kline
ID: 24330343
Is your current zone AD Integrated?  You could change it to primary and export it (to be safe) then the new ADI zone could have the same name.
The ADI zone will populate the new entries
What is wrong with your current zone?
Thanks
Mike
0
 
LVL 57

Expert Comment

by:Mike Kline
ID: 24330376
Man o Man...a coworker came by and I didn't refresh in time.... wait I never surf EE at work haha
I should have known Chris would have been all over the DNS questions
 nicely done Chris :)
Thanks
Mike
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
LVL 70

Expert Comment

by:Chris Dent
ID: 24330385

lol no worries, happens to everyone :)

Chris
0
 

Author Comment

by:MushroomStamp
ID: 24330623
The current zone "OurDomain" is on the current DC. I am replacing the current DC with a new one.  Part of the process of setting up the new one is setting up the DNS server. I DO NOT want all the old garbage from the current DNS server, hence the reason I want to start from scratch. I am following the MS Tech steps for replacing a DC. Before I transfer FSMO roles and such I need to setup the new DNS server.  I can not setup the new DNS server using the same zone name while the current one is still in use.
0
 

Author Comment

by:MushroomStamp
ID: 24330686
We have had a multitude of problems with the current DNS server... it's pretty much bubble gummed with things such as entries that can't be gotten rid of and setttings that don't take.. plenty of problems with it.

How would I seamlessly have the new DC (soon to be the only) take over the DNS role from current garbage. I don't want to important anything from current setup. I will manually enter the values of each fixed IP on the network (about 15). I can't have any down time
0
 
LVL 70

Accepted Solution

by:
Chris Dent earned 500 total points
ID: 24330696

You can if you change the zone to Standard Primary (in the Zone Properties within the DNS Console, select Change next to Type, and remove the tick from Store in Active Directory). It being integrated with AD is optional and counter productive in this instance.

You absolutely cannot use a zone name that is different from the AD Domain Name. It won't do you a bit of good.

If it's causing such problems you may as well just delete the existing zone now. Change all clients and servers to refer to the DNS service on the new DC, it will repopulate there. Then delete the current zone. That way you can add a new AD Integrated zone without being troubled by the old one.

As you're going to need to talk to the current DC to maintain replication you'll want the old DC to register Service Records and Names on the new DNS Service.

Chris
0
 
LVL 70

Assisted Solution

by:Chris Dent
Chris Dent earned 500 total points
ID: 24330713

If you can't have downtime change the zone to Standard Primary. The new zone you create will also have to be Standard Primary (not stored in AD) until you have everything in place or it will overwrite the old zone on the old DC.

After it's populated you can change the zone to AD Integrated and it will copy the current zone over without anyone noticing.

Chris
0
 

Author Closing Comment

by:MushroomStamp
ID: 31579179
Thank you sir for your quick attention to my issue.  I love this site, you guys save me so much time.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

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

Suggested Solutions

Resolve DNS query failed errors for Exchange
This article runs through the process of deploying a single EXE application selectively to a group of user.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

772 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