Comments on: Gentoo, OpenLDAP und BIND http://blog.scherbaum.info/2008/07/20/gentoo-openldap-und-bind/ Tagebuch eines Hardwaresammlers ... Thu, 28 Apr 2011 12:08:28 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Tobias Scherbaum http://blog.scherbaum.info/2008/07/20/gentoo-openldap-und-bind/comment-page-1/#comment-36452 Tobias Scherbaum Wed, 22 Oct 2008 18:19:59 +0000 http://blog.scherbaum.info/?p=205#comment-36452 Sorry, no details on this problem. In my (test) configuration I have no terminating dot neither in named.conf, nor does zoneName have one. Don't know what GoSA is doing there - is GoSA the only application where you've seen the terminating dot? Sorry, no details on this problem. In my (test) configuration I have no terminating dot neither in named.conf, nor does zoneName have one. Don’t know what GoSA is doing there – is GoSA the only application where you’ve seen the terminating dot?

]]>
By: Andreas Piening http://blog.scherbaum.info/2008/07/20/gentoo-openldap-und-bind/comment-page-1/#comment-30799 Andreas Piening Wed, 01 Oct 2008 13:05:52 +0000 http://blog.scherbaum.info/?p=205#comment-30799 Thank you for your work. I have bind version 9.5.0_p2-r1 and my LDAP-lookup works, but there's one thing I wonder about: I use GoSA (http://gosa.gonicus.de/) to manage the ldap-entries. GoSA inserts my zone as "zoneName=myzone.de." (regard the trailing dot). Bind doesn't find this zone, since it searches for "zoneName=myzone.de" (without the dot!). In my named.conf the zone definition includes the terminating dot, which makes sense. I don't exactly know if it is correct or not to insert the zoneName with the trailing dot in the LDAP-tree, since I have seen both. In text-file-based bind-config the dot must exist to terminate the top-level zone. Do you know andything about this conflict? Thank you for your work.
I have bind version 9.5.0_p2-r1 and my LDAP-lookup works, but there’s one thing I wonder about: I use GoSA (http://gosa.gonicus.de/) to manage the ldap-entries. GoSA inserts my zone as “zoneName=myzone.de.” (regard the trailing dot). Bind doesn’t find this zone, since it searches for “zoneName=myzone.de” (without the dot!).
In my named.conf the zone definition includes the terminating dot, which makes sense. I don’t exactly know if it is correct or not to insert the zoneName with the trailing dot in the LDAP-tree, since I have seen both. In text-file-based bind-config the dot must exist to terminate the top-level zone.
Do you know andything about this conflict?

]]>