PowerDNS LDAP Backend/Migration - Revision history

Nose: removed backlink

2008-06-22T12:41:24Z

removed backlink

2008-04-06T21:00:29Z

‎Bind LDAP backend

2008-04-06T20:58:47Z

‎Bind LDAP backend

2008-04-06T20:47:39Z

‎Bind LDAP backend

2008-04-06T20:40:56Z

‎Bind LDAP backend

2008-04-06T20:24:02Z

‎Bind LDAP backend

2008-04-06T20:23:49Z

‎Bind LDAP backend

2008-04-06T20:22:52Z

‎Bind LDAP backend

2008-04-06T20:21:47Z

bind ldap migration

2007-05-17T14:50:28Z

← Older revision		Revision as of 12:41, 22 June 2008
Line 69:		Line 69:
	zone2ldap --zone-name=$DOMAIN --zone-file=$DOMAIN.zone> $DOMAIN.ldif;		zone2ldap --zone-name=$DOMAIN --zone-file=$DOMAIN.zone> $DOMAIN.ldif;
	done		done
−
−
−	~~----~~
−	~~Back to [[PowerDNS LDAP Backend\|Overview]]~~

@@ Line 42: / Line 42: @@
 == Bind LDAP backend ==
-If you are using the [http://bind9-ldap.bayour.com/ Bind LDAP sdb backend], you can use the records in the LDAP tree also for the PowerDNS LDAP backend. The schemas both backends utilize is almost the same exept for one important thing: Domains for PowerDNS are stored in the attibute "associatedDomain" whereas Bind stores them split in "relativeDomainName" and "zoneName".
+If you are using the [http://bind9-ldap.bayour.com/ Bind LDAP sdb backend], you can keep the records in the LDAP tree also for the PowerDNS LDAP backend. The schemas both backends utilize is almost the same exept for one important thing: Domains for PowerDNS are stored in the attibute "associatedDomain" whereas Bind stores them split in "relativeDomainName" and "zoneName".
 There is a [http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap migration script] which creates a file in LDIF format with the necessary LDAP updates including the "associatedDomain" and "dc" attributes. The utility is executed on the command line by:

@@ Line 42: / Line 42: @@
 == Bind LDAP backend ==
-If you are using the LDAP sdb backend for the Bind DNS server, you can use the records in the LDAP tree also for the PowerDNS LDAP backend. The schemas both backends utilize is almost the same exept for one important thing: Domains for PowerDNS are stored in the attibute "associatedDomain" whereas Bind stores them split in "relativeDomainName" and "zoneName".
+If you are using the [http://bind9-ldap.bayour.com/ Bind LDAP sdb backend], you can use the records in the LDAP tree also for the PowerDNS LDAP backend. The schemas both backends utilize is almost the same exept for one important thing: Domains for PowerDNS are stored in the attibute "associatedDomain" whereas Bind stores them split in "relativeDomainName" and "zoneName".
 There is a [http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap migration script] which creates a file in LDIF format with the necessary LDAP updates including the "associatedDomain" and "dc" attributes. The utility is executed on the command line by:

@@ Line 44: / Line 44: @@
 If you are using the LDAP sdb backend for the Bind DNS server, you can use the records in the LDAP tree also for the PowerDNS LDAP backend. The schemas both backends utilize is almost the same exept for one important thing: Domains for PowerDNS are stored in the attibute "associatedDomain" whereas Bind stores them split in "relativeDomainName" and "zoneName".
-There is a [http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap migration script] which creates a file in LDIF format with the necessary LDAP updates including the "associatedDomain" and "dc" attributes. The utility is executed by:
+There is a [http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap migration script] which creates a file in LDIF format with the necessary LDAP updates including the "associatedDomain" and "dc" attributes. The utility is executed on the command line by:
   ./bind2pdns-ldap

@@ Line 54: / Line 54: @@
 The parameter "host" and "basedn" are mandatory, "binddn" is optional. If "binddn" is given, you will be asked for a password, otherwise an anonymous bind is executed. The updates in LDIF format are written to stdout and can be redirected to a file.
-The script requires Perl and the Perl Net::LDAP module and can be downloaded from [http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap /pdnsldap/bind2pdns-ldap]
+The script requires Perl and the Perl Net::LDAP module and can be downloaded from [http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap /pdnsldap/bind2pdns-ldap].
 == Other name server ==

@@ Line 47: / Line 47: @@
   ./bind2pdns-ldap
-   --host=<host anme or IP>
+   --host=<host name or IP>
    --basedn=<subtree dn>
    --binddn=<admin dn>

@@ Line 46: / Line 46: @@
 There is a [http://www.linuxnetworks.de/pdnsldap/bind2pdns-ldap migration script] which creates a file in LDIF format with the necessary LDAP updates including the "associatedDomain" and "dc" attributes. The utility is executed by:
-  ./bind2pdns-ldap \
+  ./bind2pdns-ldap
-   --host=<host anme or IP> \
+   --host=<host anme or IP>
-   --basedn=<subtree dn> \
+   --basedn=<subtree dn>
-   --binddn=<admin dn> \
+   --binddn=<admin dn>
    > update.ldif

@@ Line 1: / Line 1: @@
 __TOC__
-== BIND ==
+== BIND zone files ==
 There is a small utility in the PowerDNS distribution available called "zone2ldap", which can convert zone files used by BIND to the ldif format. Ldif is a text file format containing information about LDAP objects and can be read by every standard compliant LDAP server. Zone2ldap needs the BIND named.conf (usually located in /etc) as input and writes the dns record entries in ldif format to stdout:
@@ Line 39: / Line 39: @@
 ; --zone-name=... : Name of the zone like it is mentioned in the named.conf or in the zone file, e.g. linuxnetworks.de. Necessary if you only want to parse single zone files
 == Other name server ==

← Older revision	Revision as of 14:50, 17 May 2007
(No difference)