|
Dont know if this helps makes things
clear or not, Butttt,,,,,,,,,,,,
I use a cable modem on a home lan
running AD and you all know
AD needs DNS to install . i point the
DNS server to it's self.
AD runs 100 % like this also. I
point domain user accounts to the same DNS.
SBS runs the same , have too ,
only one domain , one DC with SBS, its hard coded this way ( SBS
).
----- Original Message -----
Sent: Sunday, June 09, 2002 11:42
AM
Subject: RE: [ActiveDir] Where should DNS
point? (Clarification)
On
initial DC setup I point DNS at a remote DC. After AD replication has taken
place I point the DC at it's own DNS server as the zone information is now in
the local copy of AD on that DC.
Ian
Moran
Konnexion Ltd
Thx for the quick replys, but I guess I didn't
really explain very well what I was asking. The question is not
whether I can run DNS on my DC, which is what I am doing. Rather, on
my TCP/IP setting on my domain controllers, should my Primary DNS setting be
set to its own IP address or to a different domain controller.
Thx again, Joe
----- Original Message -----
Sent: Thursday, June 06, 2002 8:03
AM
Subject: RE: [ActiveDir] Where should
DNS point?
Active Directory Sites and services, add subnets and assign them to
their specific sites. Clients on the specified subnets will log
on to DC's located at those sites.
DNS---from what I understand needs to be on the DC's if you plan to
use Active Directory integrated zones..(not 100% sure of that) AD
integrated zones replicate with the AD replication, so no DNS replication
schedule/scheme needs to be established.
We have three sites, DNS resides at least one DC in each
site (two in each site for redundancy) and have seen no
issues.
O'Rielly's DNS on Windows 2000 is a good resource and gives you
pretty much all the information you need.
I personally run my DNS server on a DC. How else would you
get Exchange 2000 to run on a single server? Small Business Server
also has this configuration I believe.
I was once told by a Microsoft consultant
that you should never point your DCs to themselves for DNS. (using AD
integrated DNS) So that is what I did.
However, I have since read Q article 275278, which seems to
state the contrary. I have also been having issues where my
users in remote sites will authenticate to any DC in any site at
random.
So my first question is, how should my
DNS settings be set on my DCs and secondly, what should my service
records show under _msdcs---- dc-------, _sites-------, Houston
(My Site name)-------, _tcp? Should I only see
_kerberos and _ldap entries for the servers in my site or should I
see those records for servers in that site and other
servers from other sites?
Also could anyone point me in the
direction of a good resource to describe what each of the records
under _msdcs, _sites, _tcp, _upd mean?
Thx for your time and
help....
|
