Some attribute types used in the cosine schema don't match the case were they are used. For example the aRecord attribute type is created with the name "aRecord" but used by the dNSDomain object class as "ARecord". Consequently adding dNSDomain entries to the database does not work.
Paul Bone <pbone@spelter.csse.unimelb.edu.au> writes: Maybe I'm missing something obvious, but I've never had LDAP attributes be case-sensitive. I do searches and modifies using different case from the definition of the attribute all the time, unless I'm completely spacing because it's too late.
Paul Bone <pbone@spelter.csse.unimelb.edu.au> writes: Maybe I'm missing something obvious, but I've never had LDAP attributes be case-sensitive. I do searches and modifies using different case from the definition of the attribute all the time, unless I'm completely spacing because it's too late.
Paul Bone <pbone@spelter.csse.unimelb.edu.au> writes: Maybe I'm missing something obvious, but I've never had LDAP attributes be case-sensitive. I do searches and modifies using different case from the definition of the attribute all the time, unless I'm completely spacing because it's too late.
pbone@spelter:~$ ldapvi -o dNSDomain Error: Attribute type not found: ARecord It might be ldapvi that is searching for the ARecord attribute in a case-insensative way after looking at the dNSDomain object class. I'll try using ldapadd and see if I get the same results. Thanks.
pbone@spelter:~$ ldapvi -o dNSDomain Error: Attribute type not found: ARecord It might be ldapvi that is searching for the ARecord attribute in a case-insensative way after looking at the dNSDomain object class. I'll try using ldapadd and see if I get the same results. Thanks.
pbone@spelter:~$ ldapvi -o dNSDomain Error: Attribute type not found: ARecord It might be ldapvi that is searching for the ARecord attribute in a case-insensative way after looking at the dNSDomain object class. I'll try using ldapadd and see if I get the same results. Thanks.