dNSHostName of Server object

[Stefan (metze) Metzmacher]

Hi Anatoliy,

> I noticed that when you join 2nd DC to win2k8 domain the dNSHostName attribute of the Server object in the Servers container is filled correctly by the DC which you join to. We didn't do that. I looked with wireshark when this happens but i couldn't find it on the wire so i think it was filled by the DC you are joining to during DRSR AddEntry call. The documentation doesn't say anything specific for dNSHostName being send on the wire with that call nor that we should update it then, but i figured that if we update the SPNs there it would be a good place to do that too. A patch is attached with the fix, please review it.

You should not guess:-)

- Look at the replication meta data of the dNSHostName attribute and see
if it's created in the same
  transaction as the DsAddEntry call.

- add ldap searches to the libnet_become_dc code before and after the
DsAddEntry call
  in order to see if it was added.

metze

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20100729/db335c80/attachment.pgp>