On 07/21/2010 12:34 AM, Petter Reinholdtsen wrote: > [Anders Lund] >> The perhaps best solution would be to have a RFC defining these >> attributes and object classes, but not a short term solutiong I guess. ;-) > > Yes, I believe this would be great. Might solve the problem with > incompatible implementations, as I see with bind patches, ldap2zone, > powerdns and ldapdns. :) > >> If you send me a schema file I can put it out. >> >> I might be out of office when I receive the file, and then it might take >> some time, but I will publish as soon as I have time. > > My proposed schema is attached. The attributes are copied from the > dnszone and dnsdomain2 object classes. I have not checked that their > definitions make sense, but hope their original authors did it before > they were defined. I do note that cosine.schema claim the syntax for > several of the old attributes are wrong, so I guess it is easy to get > it wrong. :)
I've included a link to the dnsattributes.schema file from http://drift.uninett.no/nett/ip-nett/oids.html now. One question. You write: The Uninett base OID for DNS records is 1.3.6.1.4.1.2428.20.2. But it should be "1.3.6.1.4.1.2428.20", shouldn't it? 1.3.6.1.4.1.2428.20.2 is the OID of the dNSDomain2 object class. - Anders -- Anders Lund <[email protected]> .~. UNINETT, N-7465 Trondheim, Norway / V \ Phone: +47 73 55 79 08 | Mob: +47 93 03 41 26 /( )\ ^ ^ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
