Strage Delay of 22 secs

Accessing sites on my server I get always the exact same delay, reason?

[AcsCh]

My Server shows a strange behaviour. Accessing a site for the first time in a timeframe of about an hour leads to a delay of 22 secs after the domain is found, just nothing happens in this time, then the site loads normaly and it is possible to browse the site normaly.

I though having some problem with the DNS of this sites, but this settings look ok to me. Anybody else had such experiences? virtual hosting on LAMP...

It's always 22 secs, not more, not less, and after IE shows page found, or opera reports connecting to site..

[MonkeeSage]

Check your DNS servers. Your primary might be dead and the secondary works or so on. If that is the case then it would take a few seconds (10-20) for the first request to timeout, and then the second would resolve fine, get cached, and you could browse the site again for as long as that cache entry lived; but you'd get the pause if you tried again after the cache was flushed or if the entry got stale. That's just a guess, though.

Jordan

[drbrain]

Is your server configured to do reverse name lookups? It could be looking up your client's reverse address.

[AcsCh]

Sound very logicaly Jordan! Thanks a lot, I will make some tests.

I don't think that's the reverse lookup, this would not take always exactely 22 secs.

[bakedjake]

Accessing a site for the first time in a timeframe of about an hour leads to a delay of 22 secs after the domain is found

Could be some bizarre component initalization or something related to sessions. Because you say that it is exactly 22 seconds, I'm not inclined to believe it is a DNS lookup either. It sounds like a piece of software firing or compiling on the fly. Check that, too.