Thanks for the answer. It looks like I didn't really include enough info to make my question clear. In the httpd.conf file of our apache 2.0.55 we have HostnameLookups ON to get the name resolution of all hosts that come our way. If there is a problem with a name server somewhere which maintains the record for the host we are trying to lookup, the thread hangs for about 12 minutes waiting for an answer. I think your suggestion wont work in my case. We are using the reverselookups in the apache logging, and how I can make apache use an external script for this purpose is somehting I have no idea about. I think also such a solution is something that would not go down well with higher up people here. Any other ideas? regards Markus On Wednesday 22 March 2006 16:38, Boysenberry Payne wrote: > What about using some kind of handler that forks its own lookup routine > outside of apache (or mod_perl, perl, phython, php, etc?) > > Thanks, > Boysenberry > > boysenberrys.com | habitatlife.com | selfgnosis.com > > On Mar 22, 2006, at 9:14 AM, Markus Mayer wrote: > > Hi All, > > > > I posted this one Thursday last week but so far got no answer, so I'll > > try > > again today. > > > > I have a small problem with some reverse lookups for which I hope > > somebody > > here might be able to help me with. > > > > Generally reverse lookups work well, but for some IP addresses the > > reverse > > lookup times out. With the help of our network admins, I was able to > > identify the problem. It is a name server problem of the ISP from > > which a > > host connects. For what ever reason, there is no answer from the > > problem > > nameserver. With HostnameLookups on, and these problem namseservers, > > apache > > waits about 12 minutes before sending any data back to the host that > > requested the page. On a normal Linux and Solaris command line, an > > nslookup, > > host, or dig fails within 10 seconds with a timeout. > > > > To get around this problem, I wanted to configure how long apache > > waits for a > > response, however I have not been able to find such an option. I also > > looked > > in the source code, but was not able to find where this timeout is set. > > Either solution is fine for me, however of course a configuration > > directive > > to set timeouts for HostnameLookups would be much more preferable. > > Does any > > one know what directive there is to set, of if there is even one? And > > if > > there's no directive, where in the source code do I look to set this? > > > > All help on this will be greatly appreciated. > > > > greetings from Austria. > > Markus > > > > --------------------------------------------------------------------- > > The official User-To-User support forum of the Apache HTTP Server > > Project. > > See <URL:http://httpd.apache.org/userslist.html> for more info. > > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|