Installing DNS on a 2003 DC
Hi, I did some searching in the Knowledge base, before proceeding with my question. I seem to have a unique situation. I have a DC on a subnet that handles our lab PCs on a private network. The DC is NOT running DNS Server services. In fact, it is not installed. I am not sure what the previous server admin was thinking, but this server in question is a DC without DNS. I thought all DC's required DNS, but some how this DC is working, well most of the time. Every once in a while I get some weird DNS issues with the lab PC's, which I believe relates back to this DC not having DNS. Now there are several other DC's that all are running AD-Integrated DNS that are on the public network. So, I am trying to figure out what would be the point of creating a DC on a private network without AD-integrated DNS on it?
So, my question for the gurus here, how do you install DNS on a current 2003 DC and make the DNS AD-Integrated?
Thanks for your time.
So, my question for the gurus here, how do you install DNS on a current 2003 DC and make the DNS AD-Integrated?
Thanks for your time.
Last Comment
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Yes all DCs are in the same domain, including the DC in question (let's call it the Lab DC). Not sure about contaminating, because they all have unique names and use NAT to gain access to the outside (Internet) for students to do research, check out library books and such.
The Lab DC has DHCP running, issuing private IP's (10.200.x.x) to the lab PCs. The DHCP is issuing the DNS server on the public(production) network.
Oh, just to clear something up, this is NOT a test lab, this is labs that our students use. The reason we put these lab PCs on a private network was we ran out of public IP's.
The Lab DC has DHCP running, issuing private IP's (10.200.x.x) to the lab PCs. The DHCP is issuing the DNS server on the public(production) network.
Oh, just to clear something up, this is NOT a test lab, this is labs that our students use. The reason we put these lab PCs on a private network was we ran out of public IP's.
ASKER
Labs consist of computer science lab, open lab, library PCs, medical assistance lab, etc.
Go through steps that I posted that is all you need
ASKER
dariusq,
Your steps are for after I install the DNS Server services on the DC in question?
Or do I perform the steps on an existing DC that has DNS Server services running?
Reason I ask is, I see the lab computers in the DNS of a DC running DNS Server services.
Thanks.
Your steps are for after I install the DNS Server services on the DC in question?
Or do I perform the steps on an existing DC that has DNS Server services running?
Reason I ask is, I see the lab computers in the DNS of a DC running DNS Server services.
Thanks.
This is on a DC that doesn't have DNS but already has the DNS role installed
ASKER
Hmmm...I am not sure if I am following you, but let me try to see if I have this right. Please bear with me.
My DCs that are running DNS Server services (as AD-Integrated DNS) are displaying all the lab computers in the DNS as correct entries in the proper DNS domain zone. But the DC that does not have DNS installed is the server that is running DHCP to serve IP's to the lab computers on our 10.200.x.x private subnet. So, I guess should I worry about this and install DNS Server services on this DC or just leave it as is? Not sure what best practice is in this scenario.
My DCs that are running DNS Server services (as AD-Integrated DNS) are displaying all the lab computers in the DNS as correct entries in the proper DNS domain zone. But the DC that does not have DNS installed is the server that is running DHCP to serve IP's to the lab computers on our 10.200.x.x private subnet. So, I guess should I worry about this and install DNS Server services on this DC or just leave it as is? Not sure what best practice is in this scenario.
ASKER
Wasn't sure if I should use a Stub Zone on this DC or use AD-Integrated DNS or just leave it alone, since it works for the most part. Just want to make sure to correct this if it needs to be.
Thanks.
Thanks.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Yes, it is best practice, which makes me wondering what the tech before me was thinking.
Anyways, how can I install DNS & make it AD Integrated zones after the server is already Domain Controller?
Thanks again.
Anyways, how can I install DNS & make it AD Integrated zones after the server is already Domain Controller?
Thanks again.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
OK, got it. During installing the DNS Server set it to use AD Integrated zones. Sorry, for some reason I thought you were saying point to a DNS zone without installing DNS Server services...which as you can see is why I was confused. Thought there was some cool feature of ADDS that I have missed. LOL
Thanks again.
Thanks again.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
What is the DNS settings being used by your LAB workstations?
Does your LAB route to your production network?
A quick test is run "nltest /dclist:domain_Name" or "Netdom query fsmo" and verify if you see your production servers.
I'd strongly suggest keeping your lab separate from the production network.
If you want or need your test lab to be integrated with production and this DC is replicating with the production network, then you can safely just added the DNS Role to this server. It should automatically start replicaiting after configuration....give it about 40 mins to get everything across your LAN.