Re: Want some help
- From: "Todd J Heron" <todd_heron_no_spam@xxxxxxxxxxx>
- Date: Sun, 10 Apr 2005 10:13:47 -0400
"mithun.pandit@xxxxxxxxx" <mithunpanditgmailcom@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:454720C9-8AC0-4303-A43F-A87814FD97D6@xxxxxxxxxxxxxxxx
>Hi Everyone,
>I am sorry to ping here, but we can surely add the ISP's IP in the TCP/Ip
>properties fo the client machines.
Yes you surely *can*, but after reading the below article when it comes to
internal Active Directory domain clients, you surely should not.
Best practices for DNS client settings in Windows 2000 Server and in Windows
Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
The only place ISP DNS servers belongs in the network is under your DNS
server's Forwarders tab, not anywhere in any place on internal AD domain
clients.
>The only disadvantage is that, in case the DNs pointer changes and points
>to the ISP's ip, then untill you reboot the machine, it will not point to
>the domain >controller's DNS.
No, not really. There would be several more disadvantages. Among these:
1) Long logon times (long waiting time for "Applying computer settings" or
clients unable to logon at all)
2) Slow boot times for DCs
3) No Active Directory replication
4) Administrators unable to manage parts of the domain
5) Group policy errors or failing outright
6) Poor (slow) network performance in general.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
.
- Follow-Ups:
- Re: Want some help
- From: ANDYZENG
- Re: Want some help
- References:
- Re: Want some help
- From: ptwilliams
- Re: Want some help
- From: mithun.pandit@gmail.com
- Re: Want some help
- Prev by Date: Macintosh <-> Active Directory
- Next by Date: Re: Macintosh <-> Active Directory
- Previous by thread: Re: Want some help
- Next by thread: Re: Want some help
- Index(es):
Relevant Pages
|