Date: Sun, 2 Oct 2011 02:00:25 -0700 From: Jeremy Chadwick <freebsd@jdc.parodius.com> To: Damien Fleuriot <ml@my.gd> Cc: Doug Barton <dougb@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: 7.3 + kqueue + apache/php + DNS lookup problem Message-ID: <20111002090025.GA78565@icarus.home.lan> In-Reply-To: <CAE63ME7wG-yr0aZdWPu15b6nBjxsUnAA0goCA2ftS=Y8xgj-Mw@mail.gmail.com> References: <4E865146.8090108@FreeBSD.org> <20111001003735.GA28346@icarus.home.lan> <4E866A70.8060203@FreeBSD.org> <CAE63ME7wG-yr0aZdWPu15b6nBjxsUnAA0goCA2ftS=Y8xgj-Mw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 02, 2011 at 10:18:30AM +0200, Damien Fleuriot wrote: > On 1 October 2011 03:18, Doug Barton <dougb@freebsd.org> wrote: > > It's a php module doing a lookup for the hostname of the back-end mysql > > server. > > > >> Are the delays always 3 seconds? > > > > Pretty much. > > > >> If so, that almost sounds like a timeout of some kind. > > > > That was my first thought, but the answer always comes eventually. > > > > To answer Chuck's questions, no threading is involved, and it's not > > apache doing the lookups. > > > > > > Doug > > > > Check your bind/unbound logs to ensure the queries are actually > successful on their first try. > > Is your DNS using forwarders ? views ? How would this explain 100% quick/reliable lookups when done from tools like nslookup and host? Same box and same resolver (127.0.0.1:53), yet different behaviour (nslookup/host vs. PHP). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111002090025.GA78565>