I don't think it *has* to.  It can be "dc=happy, dc=gumdrops" for all the
system cares.  I think some of that naming is legacy from DAP systems like
X.500, where the concept of a more global tree was in place.  I think it's
helpful to have the DC names match DNS, especially if you're going to host
several instances for different groups, and it's best to have the first "dc"
name be something that you can live with.

You can always change it later, though it's a huge PITA to do so, especially
after it goes live.  Also, use the scripts at http://www.padl.com/tools.html,
which should get you most of the way of getting your data into LDIF for
import.

Good luck!

On 8/20/07, Rudie, Tony <[EMAIL PROTECTED]> wrote:
>
> I know absolutely nothing about LDAP, despite having read a good bit of
> the "LDAP System Administration" O'Reilly book.  I'm trying to assemble just
> a rudimentary, lab, test, crash-and-burn LDAP server to experiment with NIS
> replacement ideas.  But I can't even figure out what the root node should
> be!  Does it HAVE to match my DNS domain?  Or can it be something totally
> else?  Like, say, "dn: dc=LAB-NIS"  ??  The reason I ask is that I don't
> want to have anything to do with the corporate AD server.
>
> Many thanks,
>
> Tony RudiƩ
> <[EMAIL PROTECTED]>  617 563 2509
> If we shadows have offended, think but this, and all is mended
> That you have but slumber'd here while this email did appear
> And this weak and idle theme, no more yielding, but a dream
> -  Puck, MSND V:i, updated
>
> _______________________________________________
> bblisa mailing list
> [email protected]
> http://www.bblisa.org/mailman/listinfo/bblisa
>
_______________________________________________
bblisa mailing list
[email protected]
http://www.bblisa.org/mailman/listinfo/bblisa

Reply via email to