From ded89134d4b54c7d8926f17a413fd1d6d0e51e4f Mon Sep 17 00:00:00 2001 From: Lucien Gentis Date: Wed, 5 Nov 2008 16:11:15 +0000 Subject: [PATCH] A reverse DNS lookup followed by a direct DNS lookup mean "double DNS lookup" instead of "double reverse DNS lookup" git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@711598 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_access_compat.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/mod/mod_access_compat.xml b/docs/manual/mod/mod_access_compat.xml index de03558e86d..4b9fca2e695 100644 --- a/docs/manual/mod/mod_access_compat.xml +++ b/docs/manual/mod/mod_access_compat.xml @@ -114,7 +114,7 @@ server access. Only complete components are matched, so the above example will match foo.apache.org but it will not match fooapache.org. 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 HostnameLookups directive. It will do a reverse DNS lookup on the IP address to find the associated -- 2.47.2