AIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 08, 2000 12:42 PM
Subject: RE: DNS Lookups ? huh ?
> On Thu, 8 Jun 2000, Rob Tanner wrote:
>
> > I gotta read messages all the way down before I respond.. Duh. You said
> > they were off and I told you to
--On 06/08/00 13:42:45 -0600 Marc Slemko <[EMAIL PROTECTED]> wrote:
> On Thu, 8 Jun 2000, Rob Tanner wrote:
>
>> I gotta read messages all the way down before I respond.. Duh. You said
>> they were off and I told you to turn them off. That's probably at least
>> three demerits for me.
>>
>> A
>> I knew Karyn Ulriksen would say on Jun 8 that,
KU] Uhmmm. The directive...
KU]
KU] is not HostnameLookups Off
KU] it ISHostNameLookups Off
KU]
KU] The default is on. Case sensitivity. All that... give it a whirl.
KU] We've all done it before
It's in fact case insensitif.
>
On Thu, 8 Jun 2000, Rob Tanner wrote:
> I gotta read messages all the way down before I respond.. Duh. You said
> they were off and I told you to turn them off. That's probably at least
> three demerits for me.
>
> Anyway, unless you have an extremely busy server, those lookups are
> genera
On Thu, 8 Jun 2000, Rob Tanner wrote:
> Anyway, unless you have an extremely busy server, those lookups are
> generally not that expensive.
In the general case not for you, no (except for a tied up httpd process).
But many many addresses out there have broken name server and then it will
take a
EMAIL PROTECTED]]
> Sent: Thursday, June 08, 2000 3:23 PM
> To: '[EMAIL PROTECTED]'
> Subject: Re: DNS Lookups ? huh ?
>
> No wait, this is wrong twice: see
> http://www.apache.org/docs/mod/core.html#hostnamelookups -- default is
> off and the directive names are case
's own backward compatability
sake!) :) Thx.
-Original Message-
From: Ian Kallen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 08, 2000 3:23 PM
To: '[EMAIL PROTECTED]'
Subject: Re: DNS Lookups ? huh ?
No wait, this is wrong twice: see
http://www.apache.org/docs/mod/core.html#hos
No wait, this is wrong twice: see
http://www.apache.org/docs/mod/core.html#hostnamelookups -- default is
off and the directive names are case insensitive.
Karyn Ulriksen wrote:
>
> Uhmmm. The directive...
>
> is not HostnameLookups Off
> it ISHostNameLookups Off
>
> The default is on.
> "KU" == Karyn Ulriksen <[EMAIL PROTECTED]> writes:
KU> Uhmmm. The directive...
KU> is not HostnameLookups Off
KU> it ISHostNameLookups Off
If apache doesn't recognize a configuration directive, it will puke at
you, not just silently go about its merry way.
AM
To: Paul G. Weiss; 'David Brown'; [EMAIL PROTECTED]
Subject: RE: DNS Lookups ? huh ?
I gotta read messages all the way down before I respond.. Duh. You said
they were off and I told you to turn them off. That's probably at least
three demerits for me.
Anyway, unless you ha
I gotta read messages all the way down before I respond.. Duh. You said
they were off and I told you to turn them off. That's probably at least
three demerits for me.
Anyway, unless you have an extremely busy server, those lookups are
generally not that expensive. For instance, I run TCP wr
Usually this is a result of an access rule:
deny from all
allow from *.mydomain.com
When this happens Apache needs to do a lookup on
the name even though you specified HostnameLookups
off.
I don't know what mod_perl would have had to do with
it unless the installation modified y
The problem was solved offline with the kind help of Bill Mosely, but I'll
post the solution here for the masses.
I had an entry in my httpd.conf to the tune of something like:
Deny from some.bad.domain.com
As this was a name and not an IP address, the machine had to lookup each
incoming IP add
In httpd.conf, make sure HostNameLookups is OFF. The default is ON when
you build apache (in the httpd.conf that the build generates).
-- Rob
--On Thursday, June 08, 2000 4:08 PM +0100 David Brown <[EMAIL PROTECTED]>
wrote:
> Since upgrading to the latest verion of mod_perl I've noticed tha
14 matches
Mail list logo
