DNS design questions
- From: Travis Montgomery <tmontgomery_removethis_@xxxxxxxx>
- Date: Wed, 30 Aug 2006 08:12:58 -0400
Good Morning,
We're currently at the beginning of an eDir to AD migration. We currently run DNS on linux. We've created our AD structure and enabled a DNS zone for our AD domain. Now we'd like to move our public DNS server to Windows. I'm debating whether or not to integrate our public DNS records with AD. I very much like the benefits of having DNS stored and replicated in AD however I'm concerned about exposing one of our DCs to the general public (this is a medium size college campus). I was thinking about integrating DNS on our two Domain controllers then having one member server, totally dedicated to DNS, run a secondary copy of the zone and having it exposed to the internet. As far as the "world" is concerned, this would be our primary DNS server. Would this work? Is it overkill? Is there an issue with exposing one of our DCs to the internet for DNS services? If so, what is the best way to mitigate those risks?
Thanks,
Travis
.
- Follow-Ups:
- Re: DNS design questions
- From: Herb Martin
- Re: DNS design questions
- From: Anthony
- Re: DNS design questions
- Prev by Date: I want to use my server as name server
- Next by Date: Re: DNS design questions
- Previous by thread: I want to use my server as name server
- Next by thread: Re: DNS design questions
- Index(es):
Relevant Pages
|
Loading