Maxim Dounin Wrote:
> It's to configure timeout used by nginx's own nonblocking resolver
> (http://nginx.org/r/resolver) - that is, for name resolution done
> by running nginx. To configure system resolver you should
> use your system's settings, usually /etc/resolv.conf.
>
> (Actually, sole p
Hello!
On Wed, Feb 26, 2014 at 02:32:48PM -0500, mastercan wrote:
> Hello Maxim,
>
> > On startup, nginx does name resolution of various names in a
> > configuration files, using system resolver. This includes initial
> > resolution of OCSP responders if stapling is used. If your system
> >
Hello Maxim,
> On startup, nginx does name resolution of various names in a
> configuration files, using system resolver. This includes initial
> resolution of OCSP responders if stapling is used. If your system
> resolver doesn't have internet access and blocks trying to resolve
> names - s
Hello!
On Wed, Feb 26, 2014 at 11:39:31AM -0500, mastercan wrote:
> Hello,
>
> I've encountered a problem with nginx 1.5.10.
> I'm running nginx on a highly available system (2 cluster node).
>
> When node1 fails, node2 is automatically coming into play. A few days ago
> the internet connection
Hello,
I've encountered a problem with nginx 1.5.10.
I'm running nginx on a highly available system (2 cluster node).
When node1 fails, node2 is automatically coming into play. A few days ago
the internet connection was bad - on both nodes. They could ping the gateway
only sporadically.
Node2 bec
