Re: DNS for Active Directory Only
From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 02/29/04
- Next message: Deji Akomolafe: "Re: the "." zone"
- Previous message: Deji Akomolafe: "Re: Am I making DNS harder than it really is?"
- In reply to: Dennis: "DNS for Active Directory Only"
- Next in thread: Deji Akomolafe: "Re: DNS for Active Directory Only"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 29 Feb 2004 12:37:55 -0500
All servers and workstations should specify *only* the internal
AD-integrated DNS server's IP address in their network settings. The
AD-integrated DNS server should be set up with forwarders to your ISP's DNS
servers for external resolution. Don't use any external/public DNS server
IPs in any server or client IP config or you will run into problems.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for more
info.
You probably want to start using DHCP to dish out the correct info
(including your DNS server) to clients, so you don't have to walk around and
manually configure all static addresses....
Dennis wrote:
> I'm setting up a Windows 2000 server, it will be the only
> server. We do not have an e-mail server or any other
> server that can be reached via the internet. I would like
> to know how to set up this servers DNS, so the
> workstations can keep thier exsisting DNS IP addresses.
> In other words, should I just add the IP address of the
> new server to the clients DNS server address list?
- Next message: Deji Akomolafe: "Re: the "." zone"
- Previous message: Deji Akomolafe: "Re: Am I making DNS harder than it really is?"
- In reply to: Dennis: "DNS for Active Directory Only"
- Next in thread: Deji Akomolafe: "Re: DNS for Active Directory Only"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
