A reverse DNS lookup followed by a direct DNS lookup mean "double DNS lookup" instead...

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@711598 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_access_compat.xml b/docs/manual/mod/mod_access_compat.xml
index de03558e86d44cd6183c719af98596306d414119..4b9fca2e695086b3b19368ba29fb4fe2846a2d14 100644 (file)
--- a/docs/manual/mod/mod_access_compat.xml
+++ b/docs/manual/mod/mod_access_compat.xml
@@ -114,7 +114,7 @@ server</description>
       access. Only complete components are matched, so the above
       example will match <code>foo.apache.org</code> but it will not
       match <code>fooapache.org</code>. This configuration will cause
-      Apache to perform a double reverse DNS lookup on the client IP
+      Apache to perform a double DNS lookup on the client IP
       address, regardless of the setting of the <directive
       module="core">HostnameLookups</directive> directive.  It will do
       a reverse DNS lookup on the IP address to find the associated