Why doesn't LDAP Priority and Weight change entry in the DNS?

Question

We have two Windows 2008 servers that are Active Directory Domain Controllers.  They seem to be configured properly, and are talking to each other.
I want one of the domain controllers to authenticate all of the logins because it's a more powerful box.  I want the second DC to take over if the first goes down.
I went into the Registry on the old machine, and created two 32 bit Dword registry keys as follows:
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters.
LdapSrvPriority
and
LdapSrvWeight.
Set these to 5 and 150.  Assumed the default on the faster server was 0 and 100, thus making the newer server the default choice for logon authentication.
Rebooted server.   Checked DNS, and it still is reporting 0 100 for both servers, and doing an
echo %LOGONSERVER% on various workstations seems to show that authentication is roundrobining between both servers.
Why aren't these settings sticking? And why weren't they in the registry when I started?Thanks

Answer 1

Hi,
I tested and DNS record changed as expected.
So please make sure DC you changed point to the DNS that you check. Because there will be some delay before records replicated to another DNS.
You can also check timestamp of the record if it is the latest change.
You can trigger a DNS registration manually:
How To Reregister SRV records of a Domain Controller In DNS Zone
http://support.microsoft.com/kb/556002
Hope this helps.