DNS Best Practices
From: Shaun (Shaun_at_discussions.microsoft.com)
Date: 09/22/04
- Next message: Lanwench [MVP - Exchange]: "Re: Terminal Servers Printing through USB"
- Previous message: Michael: "Explorer.exe has generated errors and will be closed by windows"
- Next in thread: Todd J Heron: "Re: DNS Best Practices"
- Reply: Todd J Heron: "Re: DNS Best Practices"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 22 Sep 2004 13:07:06 -0700
Before we get started let me set the scene. My organization is currently a
Windows NT enviroment but will soon be embarking on Active Directory 2003.
We currently have a DMZ via one-arm routing. We have three web servers in
this DMZ and all are isolated from the internal network. Currently our DNS
is outsourced but we are looking to bring it in house do to some reliability
issues we have been having with our vendor. I am thinking that it would be
best to create a Windows 2003 DNS server in our DMZ for the web servers. On
the internal network install DNS integrated with AD and have the internal
DNS/AD servers foward request for addresses outside of the internal network
to the DNS servers in the DMZ. We are looking at security and preventing
things such as footprinting. I am on the right track here, or is my maddness
flawed? Please advise
- Next message: Lanwench [MVP - Exchange]: "Re: Terminal Servers Printing through USB"
- Previous message: Michael: "Explorer.exe has generated errors and will be closed by windows"
- Next in thread: Todd J Heron: "Re: DNS Best Practices"
- Reply: Todd J Heron: "Re: DNS Best Practices"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|