Issue with 2nd DNS Controller Zone
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?
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?
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
The ADI zone will populate the new entries
What is wrong with your current zone?
Thanks
Mike
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
I should have known Chris would have been all over the DNS questions
nicely done Chris :)
Thanks
Mike
lol no worries, happens to everyone :)
Chris
ASKER
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.
ASKER
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
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
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thank you sir for your quick attention to my issue. I love this site, you guys save me so much time.
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