If you configure a subnet to be within a site, it should use the site DCs to logon as opposed to one randomly sent to it via DNS. When the local system tries to log in to AD, AD matches its IP address with a defined subnet. That subnet is associated with a site and it then tells it to log into the site's own DC.
Of course, this only works with AD-aware clients. If you have 9x clients, they need the AD client installed to take advantage of this. This is much better than doing it with DNS. Hope this helps... Marc Zukerman Senior Network Engineer Greenwich Technology Partners ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 14, 2003 8:45 AM Subject: [ActiveDir] DNS Records > > Bonjour, > > My AD Domain is managed with 6 domain controllers. > For design reasons, I have some sites without DCs attached. > When users in these sites are logging on, they are attached to one of the > DCs. > I would like to attach them, in priority, to one specific DC. > So I modified the DNS record and I put a higher priority to it. > It worked a time, but recently, all the DNS records were modified and the > default priority were restored. > > It would like to fix the priority for a long time. > How can I do that ? > > Cordialement, > F.AGNES > [EMAIL PROTECTED] > > > List info : http://www.activedir.org/mail_list.htm > List FAQ : http://www.activedir.org/list_faq.htm > List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ > List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
