[cifs-protocol] MS-ADTS: DC handling of modification to msDS-AdditionalDnsHostName
iboukris at gmail.com
Tue Jun 16 10:44:50 UTC 2020
I noticed that each time an msDS-AdditionalDnsHostName attribute is
added to a computer object (netdom/adsi/ldapmodify), Windows DC also
adds another short entry (up to the first dot if any) with a binary
This causes ldap_get_values() to fail parsing it as a string, and
ldap_get_values_len() needs to be used instead.
Looking in the docs I couldn't find any mention for this handling, and
wonder if the '\0$' is in purpose or a bug, and how it should be
handled by implementations.
More information about the cifs-protocol