Windows Server

Matt Cortner · Guest

I have about 10 computers (WinXP to Win98) connected to a win2000 server DC.
I have had the problem with the WinXP computer taking an extremely long time
to logon and access the shares on the server. I know it is a DNS issue as
all the computers have the public DNS of my ISP as their DNS settings (i.e..
64.65.xx.xxx). I have tried to set the DNS on the clients to the DNS
computer (Win2000 DC) and when I do that the network is smokin' fast but I
cannot get internet access. If I add a third DNS server to the DNS server
list on the clients the network is fast again but internet comes and goes.
I was under the impression that if client is looking for an IP (public or
private) it goes through its DNS server list and once it finds the IP it
stops searching the DNS server list. If that is true then why does internet
fail sporadically when I have all 3 DNS entries on the client computers
(primary and secondary of my ISP and private IP of my DNS server)? If I am
misinformed about how the DNS list works will someone point me in the right
direction?

Thanks a bunch!

Matt

Todd J Heron · Guest

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 domain
clients.

All internal Active Directory domain clients should be configured to use
only an internal DNS Server hosting the zone name for the Active Directory
domain. This means no workstation or server, to include all DCs and DNS
servers, on the network should be configured to use any external DNS for
resolution, not even as a secondary DNS server. The reason all domain
members and DCs must use the local DNS for DNS in TCP/IP properties, is
because that is how clients find objects in Active Directory (e.g. domain
controllers, global catalogs, etc). If you point domain clients (including
domain controllers) to a DNS server which doesn't hold this information,
expect (as you have found out some of them already by direct experience):

1) Long logon times (or clients unable to logon)
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.

ISP DNS servers belong only in the Forwarders section on an internal DNS
server.

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

HOW TO: Configure DNS for Internet Access in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Matt Cortner · Guest

PERFECT!

Thanks a bunch. That is exactly what my problem has been. Your help is
greatly appreciated by not only me but many others!

My problem was that I could not add any entries into the forwards tab as my
server was set to a root server. Through you posting I found how to resolve
this and add the appropriate entries in. Thanks again and have a great day!

Matt

"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
news:O5uHELa$EHA.2788@TK2MSFTNGP15.phx.gbl...

Todd J Heron · Guest

You're welcome.

--
Todd J Heron

	Windows Server Forum Index -> DNS	All times are GMT
Page 1 of 1