Re: Bind and OpenLDAP - ReadList.com

13 msg	Managing an Internet outage
2 msg	WPAD / PAC woes
5 msg	dnssec-keygen: a key with algorithm 'HMAC-MD5' ...
4 msg	Resolution Check
3 msg	BIND can't resolve with unreachable second NS
10 msg	special features
2 msg	Modifying BIND to provide requesting IP address...
3 msg	Setting up my MX's records to redirect mail fro...
9 msg	Multiple SOA records?

Bind and OpenLDAP
\ Arjan Hulshoff (6 May 2008)
. \ Kevin Darcy (6 May 2008)
. . \ Arjan Hulshoff (6 May 2008)
. . . \ Pedro Espinoza (7 May 2008)
. \ Marcio Garcia (6 May 2008)
. . \ Arjan Hulshoff (7 May 2008)

3 msg	bind dlz : using only Mysql
8 msg	Suggestions for coping with this issue
7 msg	Questions about Bind and AD dns integration
14 msg	Overriding MX records to internal gateways
3 msg	Bind + DKIM (ran out of space)
2 msg	time set to UTC
1 msg	Split horizon with forwarding
8 msg	Are failures cached?
2 msg	catch-all
2 msg	Problems Configuring Bind on Windows Server 2003

Subject:	Re: Bind and OpenLDAP
Group:	Bind-users
From:	Arjan Hulshoff
Date:	7 May 2008

Thanks Marcio,
Your example has helped me a lot. Only one problem with the records for
kerberos remain, however that's probably a question from the ldap
mailinglists.

Regards,
Arjan.

Marcio Garcia wrote:
> Hi,
>
> I already have some customers with BIND + LDAP.
>
> My named.conf:
>
> zone "example.pt" {
> type master;
> database "ldap
> ldap://127.0.0.1/zoneName=example.pt,dc=DNS,dc=example,dc=pt 3600";
> };
>
> My LDIF:
>
> dn: zoneName=example.pt,dc=DNS,dc=example,dc=pt
> objectClass: top
> objectClass: dNSZone
> relativeDomainName: @
> zoneName: example.pt
> dNSTTL: 3600
> dNSClass: IN
> sOARecord: example.pt. root.example.pt. 2007052900 3600
> 1800 604800 86400
> nSRecord: example.pt.
> aRecord: 10.10.10.10
>
> dn:
> relativeDomainName=www,zoneName=example.pt,dc=DNS,dc=example,dc=pt
> objectClass: top
> objectClass: dNSZone
> relativeDomainName: www
> zoneName: example.pt
> dNSTTL: 3600
> dNSClass: IN
> aRecord: 10.10.10.10
>
>
> :)
>
> Marcio Garcia
>
>
> 2008/5/6 Arjan Hulshoff <arjan.m.hulshoff>:
>
>> Hi all,
>> I need some explanation and someone who can check if my named.conf is
>> correct.
>> What needs to be explained is the database line, of course. The part
>> after ldap://localhost/ou=DNS,ou=Computers,dc=example,dc=com is a bit
>> strange to me. As far as I know this isn't standard LDAP, so what does
>> it mean and is what I have created correct?
>>
>> TIA,
>> Arjan.
>>
>>
>> options {
>> directory "/usr/local/var/state/bind";
>> pid-file "/usr/local/var/run/named.pid";
>> check-names master fail;
>> check-names slave warn;
>> check-names response ignore;
>> };
>>
>> zone "example.com" in {
>> type master;
>> database "ldap
>> ldap://localhost/ou=DNS,ou=Computers,dc=example,dc=com,o=DNS,dc=example,dc=com,d c=no
>> 10800";
>> };
>>
>> zone "56.168.192.in-addr.arpa" in {
>> type master;
>> database "ldap
>> ldap://localhost/ou=DNS,ou=Computers,dc=example,dc=com,o=DNS,dc=56,dc=168,dc=192 ,dc=in-addr,dc=arpa,dc=no
>> 10800";
>> };
>>
>> zone "0.0.127.in-addr.arpa" in {
>> type master;
>> database "ldap
>> ldap://localhost/ou=DNS,ou=Computers,dc=example,dc=com,o=DNS,dc=0,dc=0,dc=127,dc =in-addr,dc=arpa,dc=no
>> 10800";
>> };
>>
>> zone "." in {
>> type hint;
>> database "ldap
>> ldap://localhost/ou=DNS,ou=Computers,dc=example,dc=com,o=DNS,dc=no 10800";
>> };
>>
>>
>>
>>
>>
>
>
>