Kevin

I have confirgured the DHCP as discussed, with it responsible for registering
and updating all clients in DNS. I have made the server part of the
DNSupdateproxy group and created a dedicated user account to authenticate for
secure updates to work.

Now when a client obtains a DHCP lease, the server DOES register its Host
and PTR records but the owner of said records is SYSTEM. I was expecting the
user account I created for authentication to be the owner, is this incorrect?

Otherwise how do i verify this configuration works?

Thanks for any assistance you can offer, you been a great so far

Regards

S

si wrote:
>Hi
>
>Again thanks, I meant add the dhcp server to the DNSupdateproxy group, not
>the user account. Is this incorrect? I understand it is required so DNS
>records created by the server are updatable (ie ownership can change) by an
>appropriate client/other DHCP server, request.
>
>This is a test environment for learning purposes.An environment where
>multiple DHCP servers is used is reasonable to expect, I understand for these
>other servers to be able to update other DHCP server created DNS records the
>above scenario (along with a dedicated user account for authentication) is
>required for secure dynamic updates to operate correctly.
>
>I think I am getting there...
>
>Thanks for you advice
>
>Cheers
>
>S
>
>>Read inline please.
>>
>[quoted text clipped - 19 lines]
>>passwords. This basic rule gives you at least 10 to the 27th power password
>>combinations.

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forum...r-dns/200706/1