PowerDNS LDAP Backend/Optimization - Revision history

Nose: Revert vandalism

2010-06-17T20:19:42Z

Revert vandalism

2010-06-17T20:18:07Z

Reverted edits by 122.49.210.50 (Talk) to last version by 119.111.124.194

2010-06-09T17:34:27Z

‎LDAP indices

2010-06-09T17:33:58Z

‎LDAP indices

2008-06-22T12:41:41Z

removed backlink

2007-05-17T14:50:52Z

2007-05-06T17:08:55Z

header hierarchy

2007-04-21T20:58:45Z

2007-04-15T10:49:10Z

Pdnsldap optimization moved to PowerDNS LDAP Backend - Optimization

2006-05-01T12:12:40Z

‎Access method

@@ Line 3: / Line 3: @@
 == LDAP indices ==
-http://www.casino-spielen.biz/ casino deutschland]
+To improve performance, you can tell the LDAP server to maintain indices on certain attributes. This leads to much faster searches for these type of attributes.
-−
-To improved performance, you can tell the LDAP server to maintain indices on certain attributes. This leads to much faster searches for these type of attributes.
 The LDAP DNS backend mainly searches for values in associatedDomain, so maintaining an index (pres,eq,sub) on this attribute is a big performance improvement:

@@ Line 3: / Line 3: @@
 == LDAP indices ==
-[http://www.casino-spielen.biz/ casino deutschland]
+http://www.casino-spielen.biz/ casino deutschland]
 To improved performance, you can tell the LDAP server to maintain indices on certain attributes. This leads to much faster searches for these type of attributes.

@@ Line 3: / Line 3: @@
 == LDAP indices ==
-http://www.casino-spielen.biz/ casino deutschland]
+[http://www.casino-spielen.biz/ casino deutschland]
 To improved performance, you can tell the LDAP server to maintain indices on certain attributes. This leads to much faster searches for these type of attributes.

← Older revision		Revision as of 17:33, 9 June 2010
Line 2:		Line 2:

	== LDAP indices ==		== LDAP indices ==
		+
		+	http://www.casino-spielen.biz/ casino deutschland]

	To improved performance, you can tell the LDAP server to maintain indices on certain attributes. This leads to much faster searches for these type of attributes.		To improved performance, you can tell the LDAP server to maintain indices on certain attributes. This leads to much faster searches for these type of attributes.

← Older revision		Revision as of 12:41, 22 June 2008
Line 25:		Line 25:

	The method of accessing the entries in the directory affects the performance too. By default, the "simple" method is used search for entries by using their associatedDomain attribute. Alternatively you can choose the "tree" method, whereby the search is done along the directory tree, e.g. "host.example.dom" is translated into "dc=host,dc=example,dc=dom,...". This requires your LDAP DNS subtree layout to be 1:1 to the DNS tree, but then you will gain additional 7% better performance values		The method of accessing the entries in the directory affects the performance too. By default, the "simple" method is used search for entries by using their associatedDomain attribute. Alternatively you can choose the "tree" method, whereby the search is done along the directory tree, e.g. "host.example.dom" is translated into "dc=host,dc=example,dc=dom,...". This requires your LDAP DNS subtree layout to be 1:1 to the DNS tree, but then you will gain additional 7% better performance values
−
−
−	~~----~~
−	~~Back to [[PowerDNS LDAP Backend\|Overview]]~~

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

@@ Line 1: / Line 1: @@
 __TOC__
 == LDAP indices ==
@@ Line 22: / Line 20: @@
 == dNSTTL attribute ==
-Converting the string in the dNSTTL attribute to an integer is a time consuming task. If you don't use a seperate TTL value for each entry and use the default-ttl parameter in pdns.conf instead, you will gain a ca. 7% better performance for entries that aren't cached. You can still add a dNSTTL attribute to entries that should have a different TTL than the default TTL
+Converting the string in the dNSTTL attribute to an integer is a time consuming task. If you don't use a separate TTL value for each entry and use the default-ttl parameter in pdns.conf instead, you will gain a approx. 7% better performance for entries that aren't cached. You can still add a dNSTTL attribute to entries that should have a different TTL than the default TTL
 == Access method ==

@@ Line 7: / Line 7: @@
 To improved performance, you can tell the LDAP server to maintain indices on certain attributes. This leads to much faster searches for these type of attributes.
-The PowerDNS LDAP backend mainly searches for values in associatedDomain, so maintaining an index (pres,eq,sub) on this attribute is a big performance improvement:
+The LDAP DNS backend mainly searches for values in associatedDomain, so maintaining an index (pres,eq,sub) on this attribute is a big performance improvement:
   index associatedDomain pres,eq,sub
-Furthermore if you set ldap-method=strict, it uses the aRecord and aAAARecord attribute for reverse mapping of ip addresses to names. To maintain an index (pres,eq) on these attributes also improves performance of the LDAP server:
+Furthermore if you set ldap-method=strict, it uses the aRecord and aAAARecord attribute for reverse mapping of IP addresses to names. To maintain an index (pres,eq) on these attributes also improves performance of the LDAP server:
   index aAAARecord pres,eq

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

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

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