DNS as it relates to DNS
- From: "Cary Shultz" <cshultz@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Dec 2007 08:28:25 -0500
Good morning!
I continually run into this issue with my colleagues so I am posting here so
that others might give their thoughts and opinions on this subject....
What exactly is the problem with providing computers that are joined to an
AD environmnet (WIN2003 in most cases...some WIN2003 R2) with Public DNS
information in the TCP/IP configuration information?
Meaning, DHCP (a Windows Sever) hands out an IP Address lease with all of
the usual suspects....Options 003, 006, 015, 044 and 046. When handing out
the IP Addresses for the DNS Server (let's say that there are two Domain
Controllers in this single AD Domain / Forest, both of which are running
DDNS) what is wrong with handing out those two internal IP Addresses as well
as two Public DNS Servers to all of your workstations (let's just say the IP
Addresses of the two DNS Servers that you ISP provides you)?
What difference does it make if you hand out the Public DNS Servers' IP
Addresses as long as the "Prefered DNS Server" is one of those two internal
DNS Servers and the "Alternate DNS Server" is the other internal DNS Server?
Thanks all!
Cary
.
- Follow-Ups:
- Re: DNS as it relates to DNS
- From: Cary W. Shultz
- Re: DNS as it relates to DNS
- From: Joe D
- Re: DNS as it relates to DNS
- From: Paul Bergson [MVP-DS]
- RE: DNS as it relates to DNS
- From: Jimmy Benandex
- Re: DNS as it relates to DNS
- Prev by Date: Re: Advanced page cannot be opened
- Next by Date: Re: GPO replication
- Previous by thread: application directory partition
- Next by thread: RE: DNS as it relates to DNS
- Index(es):
Relevant Pages
|