SMcDonald666
asked on
How do I set up DNS on a simple 2008 R2 Server for a 35 computer network?
I have a small network of 35 computers all in one location. We have a comcast cable modem that acts as our Gateway, DHCP, and I assume our DNS since I'm using a Novell 5.1 file server only.
I would like to migrate to a Windows Server 2008 R2 and use active directory which would require us to have the server run DNS. This server will not be accessible on the web. It will be a LAN only.
Since I won't be putting this server on the WEB do I have to use a registered domain name? Can I just use: corp.buisnessname.org? (as an example). Do I need to do anything with the comcast cable modem? It currently points to a static IP address and 2 DNS addresses. Does my DNS once active on the 2008 R2 Server take over for this? Do I point the server to the modem/router?
Is there a simple step by step guide out there? I would think with this being the most basic of setups for server 2008 R2 there would be a nice step by step guide out there. Do I need forward look up zones with this simple a setup? Would really appreciate someone directing me to a simple and plan instruction manual on this type of setup. Once setup up I plan on using this as a simple file server only. Nothing else. I don't like the delays with workgroups...we need the security of active directory.
Thanks
Scott McDonald
I would like to migrate to a Windows Server 2008 R2 and use active directory which would require us to have the server run DNS. This server will not be accessible on the web. It will be a LAN only.
Since I won't be putting this server on the WEB do I have to use a registered domain name? Can I just use: corp.buisnessname.org? (as an example). Do I need to do anything with the comcast cable modem? It currently points to a static IP address and 2 DNS addresses. Does my DNS once active on the 2008 R2 Server take over for this? Do I point the server to the modem/router?
Is there a simple step by step guide out there? I would think with this being the most basic of setups for server 2008 R2 there would be a nice step by step guide out there. Do I need forward look up zones with this simple a setup? Would really appreciate someone directing me to a simple and plan instruction manual on this type of setup. Once setup up I plan on using this as a simple file server only. Nothing else. I don't like the delays with workgroups...we need the security of active directory.
Thanks
Scott McDonald
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do you already have a Microsoft Active Directory Domain internally? You will need this for DNS to work properly. You will want to use an internal FQDN such as businessname.local rather than a .org. There are certificate ramifications to using a top level domain internally, and changing is tougher than making it right in the first place. That being said...
Run the Add Role wizard and select AD DS. This will create a new domain in a new forest named what you give it. Then it will launch the DCPROMO wizard. It will automatically install DNS as well. Make sure that the server has a static IP address, and once installed, point its NIC to itself as DNS server. You will likely want to install DHCP as well, and create a scope option for DNS to point at the Windows server.
Hope this helps.
Run the Add Role wizard and select AD DS. This will create a new domain in a new forest named what you give it. Then it will launch the DCPROMO wizard. It will automatically install DNS as well. Make sure that the server has a static IP address, and once installed, point its NIC to itself as DNS server. You will likely want to install DHCP as well, and create a scope option for DNS to point at the Windows server.
Hope this helps.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Your scenario is pretty simple.
Install Server OS
Configure it with a static IP
Run dcpromo
*You don't need a real FQDN. Setup your AD domain with mycompany.local
*Later, configure DNS to forward all other lookups to comcast.
Finally, create user accounts and join workstations to the new ad domain
Install Server OS
Configure it with a static IP
Run dcpromo
*You don't need a real FQDN. Setup your AD domain with mycompany.local
*Later, configure DNS to forward all other lookups to comcast.
Finally, create user accounts and join workstations to the new ad domain
ASKER
I've not added this server to the network yet. We are still on the Novell 5.1 server and login system. My plan is to get this new 2008 R2 up and running with my machine connecting to it and then role it out. When you say point my clients in there TCPIP properties, does this mean I turn off automatically obtain IP address etc? I know I'll need to change all the clients from workgroup to domain, but wasn't sure if I'd need to change IP addressing. Pointing the DNS server to itself is 127.0.0.1 correct? Can I get DNS running without also going with DHCP? Or should I do both at the same time. So I keep the router the same unless I move DHCP role to the new DNS server? I use 192.168.0.1 as the gateway for printers etc. No changes there correct?
ASKER
My server will be connected to the internet. We have no plans at this time for a VPN. So outside the office access is done by Radmin.
You don't need to change anything IP wise. Just make sure you give the new server a static IP and make sure DHCP is ready to run before you disable DHCP service on the router.
The gateway wont change - you will need to specify the same gateway address in your dhcp pool.
The gateway wont change - you will need to specify the same gateway address in your dhcp pool.
Point the clients however you do it but usually DHCP you need to make sure clients are going to Server for DNS not external DNS servers.
You should use the actual IP address of the server not 127.0.0.1 loopback address.
Keep the router the same you can use DNS without DHCP but I recommend that you disable DHCP on router and allow Windows to be your DHCP server
You should use the actual IP address of the server not 127.0.0.1 loopback address.
Keep the router the same you can use DNS without DHCP but I recommend that you disable DHCP on router and allow Windows to be your DHCP server
This is a basic step by step guide:
1. Turn off DHCP Server on Comcast (Windows 2008 R2 has much better options like client reservation and secure dynamic updates in DNS zones)
2. Install Windows 2008 R2 server, and point primary DNS server on NIC tcp/ip v4 properties to itself ( this is required for AD to work)
3. Install Active Directory domain services and choose name for new domain (you can also use corp.local or whatever you want)
4. Install DHCP Server role and create new DHCP scope for your clients. (make sure that DNS server address in your scope is IP address of AD server not router)
5. Join computers to domain.