If you need resolver to your configuration, you can use upstream {...}.
Nginx resolve hostnames from upstreams in config parsing stage.


On Thu, Jan 14, 2010 at 4:09 AM, Gabriel Ramuglia <gabe@vtunnel.com> wrote:

> If resolvers are causing this issue for you, you should run your own
> local resolvers. Even googles will have issues from time to time.
>
> I've dealt with this a few times and wrote up an article in 2007 to
> help with this problem:
>
>
> http://www.freeproxies.org/blog/2007/12/15/dealing-with-a-common-issue-in-proxies-dns-resolution-failure/
>
> On Wed, Jan 13, 2010 at 2:56 PM, vicky007 <nginx-forum@nginx.us> wrote:
> > Hello,
> >
> > I'm using nginx as reverse proxy to apache. Apache only serves php
> because I had no time to set up fastcgi or php-fpm on this box.
> >
> > Anyway, today there was sudden increase in nginx writing connections and
> increase of apache processes. It already happened to me in past and cause
> was the datacenter resolvers (at least switching to google resolvers fixed
> it immediately). Today the change of resolvers does not do anything.
> >
> > Here are graphs to show the situation:
> http://ultranet.sk/~temp/weird.PNG http://ultranet.sk/%7Etemp/weird.PNG
> >
> > Anyone experienced something similar? What can be wrong?
> >
> > Thank you.
> >
> > vicky
> >
> > Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,40894,40894#msg-40894
> >
> >
> > _______________________________________________
> > nginx mailing list
> > nginx@nginx.org
> > http://nginx.org/mailman/listinfo/nginx
> >
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>



--
Faithfully yours, Eugenie
ICQ #701217
GTalk ekruglov@gmail.com
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx