DNS, Active Directory, and public domains....
- From: "unc27932" <unc27932@xxxxxxxxx>
- Date: 13 Apr 2005 19:25:28 -0700
I'm looking to upgrade a small office environment workgroup to use
Active Directory & have some networking setup & DNS questions - I'm new
at this....if you're still interested the specs are below....
8-10 Workstations - all XP or 2K pro
1 Server - W2K Server
1 Hub, plugged into Router - out to internet/university network
We are in a university network, so we all have static IPs that reside
in the block of IPs given to us by the university admins.
XXX.YY.ZZ.64-128, subnet 255.255.255.192 I think??? All are publicly
viewable IPs, which I'd also currently like to change in the future,
using DHCP on the server perhaps. We currently exist only as a
workgroup, with security policies, permissions, management, etc.
happening on each workstation. I want to centralize these things &
learn about AD in the process.
My questions are....
1) There seem to be differing opinions on whether or not the AD domain
needs to match an Internet domain. In our example, we're part of the
university, and we do have an internet subdomain on their domain (i.e.
each computer we have has a public entry of
computer1.ouroffice.university.edu, where "university" is our
university, obviously, and "ouroffice" is the subdomain). So when
naming my Active Directory domain, do I name it:
ouroffice.university.edu
OR
ouroffice.local????
2) Currently all workstations & server (currently only acting as a
file server, no AD) plug into the hub/switch, which is then plugged
into the router & out to the internet. If I want to gradually do this
process, can I set up a private network on the same hardware, using the
server as the DHCP server? Do I need to physically separate hardware,
or is everything fine on the same switch/router?
3) Do I assign a private IP to the DHCP/AD machine or public IP? Does
it matter? Either way I suppose that machines that I want to log into
my AD domain need to be on the same subnet, right?
The way I'm envisioning my process is the following....tell me where
I'm wrong....
1-upgrade my W2K to use Active Directory
2-change IP to private IP (192.168...blah, blah)?? Or leave public?
Also assign subnet (255.255.255.192? or 255.255.255.0)
3-Modify client machines to join the ouroffice.local (or
ouroffice.university.edu) domain
4-Modify the clients to accept DHCP
5-Modify the DNS config on AD to forward external DNS requests to
university DNS servers??
Sorry for the long message - I look forward to the responses.
.
- Follow-Ups:
- Re: DNS, Active Directory, and public domains....
- From: Herb Martin
- Re: DNS, Active Directory, and public domains....
- Prev by Date: Re: DNS gives UnKnown to nslookup Default Server results
- Next by Date: Re: Unix Bind and Windows DNS coexist problem with forwarder ON
- Previous by thread: DNS replication
- Next by thread: Re: DNS, Active Directory, and public domains....
- Index(es):
Relevant Pages
|
