Re: Site Question
- From: Ulf B. Simon-Weidner [MVP] <nospam2-ulf@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 30 Oct 2005 19:11:46 +0100
Wolfgang Scholz says...
> hi ulf,
>
> that was exactly what happened. when i checked the _ldap and _kerberos
> records of site A in the dns i saw also records from domain controller B. i
> have absolutely no idea why and how this records came in. we created the
> sites with the standard mmc snap in, not something special. the interesting
> thing is, i deleted the sites with the "active directory sites and services"
> . i noticed that a deletion of a site with the snap in does not invoke a
> deletion in the dns also. so i deleted the sites manually in the dns. after
> the replication, the sites were completely gone. when i recreated the sites
> all dns records got created correct. so now i have a site A with records
> from domaincontroller A and a site B with records from domain controller B.
> at least my sites are working now but i have no idea why they got created
> wrong which makes me a little bit nervous. by the way i found a great
> article from ms regarding this topic:
> http://support.microsoft.com/kb/306602/en-us . do you know other articles or
> whitepapers with a detailed description of sites and dns and when will be
> what created in the zones ?
>
> thanks for the help
>
Hi Wolfgang,
you're welcome. What is usually happening is that you create a new site, but
don't have a DC assigned to it right away. Another DC will find that the site
has no DC, and via Automatic Site Coverage decides to advertise himself for the
site without DC. Then you are going to move a DC to that site, however the
other record will not be deleted automatically. Usually if you configure DNS
Aging and Scavening (der Aufräumvorgang) it'll take care of those stale
records.
What I would have done is just deleting the wrong records, but you've got the
same entries by deleting the site and recreating it (also I usually wouldn't do
that, to much work).
When you deleted the same thing happens. Active Directory Sites and Services
will never create or edit DNS-Entries, it's the Server itself which figures out
which DNS-Entries he should write and then he's publishing those to the DNS-
Server. So when you delete a site usually the records get staled (not
refreshed) and will be deleted by DNS Aging and Scavening.
References: There's a lot of good stuff on microsoft.com, especially when you
look at the ressource kit (which you are also able to buy to read offline).
Here's a reference of the behavior in W2k which still applies:
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-
us/distrib/dsbc_nar_jevl.asp
But you'll find more using a search engine, that's what I'd do to find you some
articles as well. If you are in for some deep background info look into the
TechCenters on Microsoft.com, e.g. here's the link for the WS2k3 Deployment
Guide:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/c
283b699-6124-4c3a-87ef-865443d7ea4b.mspx
--
Gruesse - Sincerely,
Ulf B. Simon-Weidner
MVP-Book "Windows XP - Die Expertentipps": http://tinyurl.com/44zcz
Weblog: http://msmvps.org/UlfBSimonWeidner
Website: http://www.windowsserverfaq.org
.
- Follow-Ups:
- Re: Site Question
- From: Wolfgang Scholz
- Re: Site Question
- References:
- Re: Site Question
- From: Paul Hinsberg
- Re: Site Question
- From: Wolfgang Scholz
- Re: Site Question
- From: Ulf B. Simon-Weidner [MVP]
- Re: Site Question
- From: Wolfgang Scholz
- Re: Site Question
- Prev by Date: Re: Timr service
- Next by Date: Re: Timr service
- Previous by thread: Re: Site Question
- Next by thread: Re: Site Question
- Index(es):
Relevant Pages
|