The top entry in a LDAP DIT (Directory Information Tree) is, in the LDAP world, variously referred to as the root, the base or the suffix depending on the document, its author, day of the week or some other variable unknown to us.
In the documentation, the subject of the root (a.k.a. suffix or base) is frequently treated in one of two ways. It's assumed to be an automagic thing that is the beyond the scope of mere mortals to understand and handled in a ritualistic way as if it had been handed down from one generation to another (or possibly on tablets or stone) and certainly no attempt is made to explain it. Conversely the other camp handles it at extreme length usually accompanied by much wailing, gnashing of teeth and incantations to the twin gods of the ITU and the IETF.
Our advice - unless you need to make the directory globally available define the root as an ou=gobbledegook and spend no more time on the subject. Defining a simple root or suffix.
Now for the serious stuff.
The angst stems for the original and laudable goal of X.500 - apparently continued by the IETF - to have a global hierarchy of directories not dissimilar to the DNS system for those familiar with that architecture.
In this context the root (a.k.a. suffix, base), which would be exposed globally plays a significant role - it must be unique. Back to our advice, unless you will expose the directory at some stage in the future - forget it - give it whatever name you want - meaningful or humourous as you desire. Defining a simple root or suffix.
If you have, or may in the future have, global ambitions then read on.
X.500 chose a root standard based on ou=organisation name,c=country code, such as ou=Example Inc., c=us, for the reason - perhaps - it seemed like a good idea at the time or it was Thursday. More on ou definitions. Defining an X.500 format root or suffix.
The IETF (through the INFORMATIONAL only RFC 2247) chose to use a domain name structure, for instance dc=example, dc=com. Partly because it was based on DNS domain names which are intrinsically globally unique and partly on a somewhat more specious argument that says - given either a DNS SRV record or an LDAP server name - you can discover the suffix. Thus, if the LDAP server name is ldap.example.com (obtained directly or via an SRV RR) then it would be resonable to assume that the suffix would be dc=example,dc=com. Not terribly convincing. Defining an RFC 2247 format root or suffix.
And if you don't have a domain name - well that's just too bad. If you have multiple domain names which one should you choose - it does not matter (you can even use all of them) since every domain name is unique.
In the diagram below - all three are valid root entries. Two of which could be globally unique - one certainly is not. Phew!
Problems, comments, suggestions, corrections (including broken links) or something to add? Please take the time from a busy life to 'mail us' (at top of screen), the webmaster (below) or info-support at zytrax. You will have a warm inner glow for the rest of the day.
3 ldap objects
4 install ldap
7 replica & refer
10 ldap api
14 ldap tools
notes & info
rfc's & x.500
This work is licensed under a Creative Commons License.
If you are happy it's OK - but your browser is giving a less than optimal experience on our site. You could, at no charge, upgrade to a W3C STANDARDS COMPLIANT browser such as Firefox