[Ldapdns-users] DC tree structure
Brought to you by:
nimh
From: <ib...@eu...> - 2006-12-23 17:45:53
|
Hi, this is my first message to the list. I'm trying ldapdns for fisrt time. I've got making it working, but have som= e=20 dudes about the LDAP structure I need for it. In my example I have a domain "mydomain.org" so my LDAP top is: dc=3Dmydomin,dc=3Dorg Reading the doc I have created a ou for dns entries: ou=3Ddns,dc=3Dmydomin,dc=3Dorg Now I want an A record for my domain server so the only solution that worke= d=20 for me is the following: 1) Create: dn: dc=3Dorg,ou=3Ddns,dc=3Dmydomin,dc=3Dorg objectClass: dNSDomain objectClass: domainRelatedObject objectClass: top objectClass: dcObject structuralObjectClass: dNSDomain dc: org associatedDomain: net <-- * =C2=BFwhat for? 2) Create: dn: dc=3Dmydomain,dc=3Dorg,ou=3Ddns,dc=3Dmydomin,dc=3Dorg objectClass: dNSDomain objectClass: domainRelatedObject objectClass: top structuralObjectClass: dNSDomain dc: mydomain aRecord: 90.90.90.90 nSRecord: @ associatedDomain: blablabla It works fine: #> host mydomain.org 127.0.0.1 Using domain server: Name: 127.0.0.1 Address: 127.0.0.1#53 Aliases: mydomain.org has address 90.90.90.90 =2D My first question is: Do I need to separete the "dc=3Dorg" and "dc=3Dmy= domain"=20 necesarily? is not anyway just to put the following? dc=3Dmydomain.org,ou=3Ddns,dc=3Dmydomian,dc=3Dorg I think maybe using "o" instead of "dc", but isn't "o" "deprecated" for it? =2D Second question (maybe not related to ldapdns): What for is the =20 associatedDomain attribute? it works even if a put "blablabla" in this fiel= d. =2D I've just started with ldapdns, am I doing something wrong in my LDAP=20 configuration? any recomendation? Thanks for all, specially to the autor of this good application. Regards. =2D-=20 I=C3=B1aki Baz Castillo |