PowerDNS LDAP Backend/Troubleshooting - Revision history

Nose: removed backlink

2008-06-22T12:42:00Z

removed backlink

Nose: /* Trying to set unexisting parameter */

2008-05-04T11:10:08Z

‎Trying to set unexisting parameter

Nose: unexisting parameter

2008-05-04T11:09:24Z

unexisting parameter

Nose: PowerDNS LDAP Backend - Troubleshooting moved to PowerDNS LDAP Backend/Troubleshooting

2007-05-17T14:51:05Z

PowerDNS LDAP Backend - Troubleshooting moved to PowerDNS LDAP Backend/Troubleshooting

Nose: header hierarchy

2007-05-06T17:09:57Z

header hierarchy

Nose: minor fixes

2007-04-21T21:00:23Z

minor fixes

Nose: Pdnsldap troubleshooting moved to PowerDNS LDAP Backend - Troubleshooting

2007-04-15T10:49:32Z

Pdnsldap troubleshooting moved to PowerDNS LDAP Backend - Troubleshooting

Nose: /* Bad search filter */

2006-05-01T12:13:21Z

‎Bad search filter

Nose: /* IPv6 reverse lookup doesn't work in strict mode */

2006-04-29T09:50:08Z

‎IPv6 reverse lookup doesn't work in strict mode

Nose: /* Bad search filter */

2006-04-23T13:46:25Z

‎Bad search filter

← Older revision		Revision as of 12:42, 22 June 2008
Line 40:		Line 40:
	----		----
	'''Feel free to add your own tips'''		'''Feel free to add your own tips'''
−
−
−	~~----~~
−	~~Back to [[PowerDNS LDAP Backend\|Overview]]~~

@@ Line 7: / Line 7: @@
   ldap-''name''=''value''
-the PowerDNS server won't start up and you will see a fatal error in the log file. For a list of available parameters, please have a look at [[PowerDNS_LDAP_Backend/Installation#Configuration_Options|configuration options]].
+the PowerDNS server won't start up and you will see a fatal error in the log file. For a list of available parameters, please have a look at [[PowerDNS_LDAP_Backend/Installation#Configuration_options|configuration options]].
 == Use of quotation marks ("") ==

← Older revision		Revision as of 11:09, 4 May 2008
Line 1:		Line 1:
	__TOC__		__TOC__
		+
		+	== Trying to set unexisting parameter ==
		+
		+	If your PowerDNS config file contains an unknown parameter or at least one of your parameters is not in the form
		+
		+	ldap-''name''=''value''
		+
		+	the PowerDNS server won't start up and you will see a fatal error in the log file. For a list of available parameters, please have a look at [[PowerDNS_LDAP_Backend/Installation#Configuration_Options\|configuration options]].

	== Use of quotation marks ("") ==		== Use of quotation marks ("") ==

@@ Line 1: / Line 1: @@
 __TOC__
 == Use of quotation marks ("") ==
-Do never use quotation marks in the PowerDNS config files! They are not evaluated and remain part of the parameter value. This leads to hard to find errors, e.g. no objects are returned from the LDAP directory.
+Do never use quotation marks in the PowerDNS configuration files! They are not evaluated and remain part of the parameter value. This leads to hard to find errors, e.g. no objects are returned from the LDAP directory.
 == No reverse zone transfer ==
@@ Line 13: / Line 11: @@
 == IPv6 reverse lookup doesn't work in strict mode ==
-For automatically generated reverse IPv6 records your AAAARecord entries must follow two restrictions: They have to be fully expanded ("FFFF::1" is not allowed and it must be "FFFF:0:0:0:0:0:0:1" instead) and they must not contain leading zeros, e.g. an entry containing "002A" is incorrect - use "2A" without zeros instead. These restrictions are due to the fact that LDAP DNS AAAA entries are pure text and doesn't allow searching by wild-cards.
+For automatically generated reverse IPv6 records your aAAARecord entries must follow two restrictions: They have to be fully expanded ("FFFF::1" is not allowed and it must be "FFFF:0:0:0:0:0:0:1" instead) and they must not contain leading zeros, e.g. an entry containing "002A" is incorrect - use "2A" without zeros instead. These restrictions are due to the fact that LDAP DNS AAAA entries are pure text and doesn't allow searching by wild-cards.
 == Bad search filter ==

@@ Line 5: / Line 5: @@
 == Use of quotation marks ("") ==
-Do never use quotation marks in the PowerDNS config files! They are not evaluated and remain part of the parameter value. This leads to hard to find errors, e.g. no objects are returned from the ldap directory.
+Do never use quotation marks in the PowerDNS config files! They are not evaluated and remain part of the parameter value. This leads to hard to find errors, e.g. no objects are returned from the LDAP directory.
 == No reverse zone transfer ==
-Your ldap tree must contain a seperate subtree of PTR records (e.g. for 1.1.10.10.in-addr.arpa) and you can't set "ldap-method" to "strict".
+Your LDAP tree must contain a separate subtree of PTR records (e.g. for 1.1.10.10.in-addr.arpa) and you can't set "ldap-method" to "strict".
 == IPv6 reverse lookup doesn't work in strict mode ==
-For automatically generated reverse IPv6 records your AAAARecord entries must follow two restrictions: They have to be fully expanded ("FFFF::1" is not allowed and it must be "FFFF:0:0:0:0:0:0:1" instead) and they must not contain leading zeros, e.g. an entry containing "002A" is incorrect - use "2A" without zeros instead. These restrictions are due to the fact that LDAP AAAA entries are pure text and doesn't allow searching by wildcards.
+For automatically generated reverse IPv6 records your AAAARecord entries must follow two restrictions: They have to be fully expanded ("FFFF::1" is not allowed and it must be "FFFF:0:0:0:0:0:0:1" instead) and they must not contain leading zeros, e.g. an entry containing "002A" is incorrect - use "2A" without zeros instead. These restrictions are due to the fact that LDAP DNS AAAA entries are pure text and doesn't allow searching by wild-cards.
 == Bad search filter ==

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

← Older revision	Revision as of 10:49, 15 April 2007
(No difference)

← Older revision		Revision as of 12:13, 1 May 2006
Line 37:		Line 37:

	----		----
−	Back to [[PowerDNS ~~ldapbackend~~\|Overview]]	+	Back to [[PowerDNS LDAP Backend\|Overview]]

@@ Line 16: / Line 16: @@
 == Bad search filter ==
-Note, that when applying ldap-filter-lookup, in user provided string (remember, no " or ' quotes!), a string part :target:
-is replaced with - without quotes - "(associatedDomain=QUERYDATA)" and braces ARE added. So if You create some filter like
+The release of PowerDNS 2.9.20 contains a bug in ldap-filter-{axfr,lookup}. A user provided string with ":target:" is replaced with "(associatedDomain=QUERYDATA)" and braces ARE added. So if you create some filter like
   ldap-filter-lookup=(&(:target:)(active=yes))
@@ Line 25: / Line 25: @@
   ldap-filter-lookup=(&((associatedDomain=QUERYDATA))(active=yes))
-which results with bad search filter. Instead You should add
+which results with bad search filter. To circumvent the bug temporarily you can add instead
   ldap-filter-lookup=(&:target:(active=yes))
-to get wanted result.
+The bug will be fixed in version 2.9.21 and later versions.
 ----