resolver directive doesn't fallback to the system DNS resolver

Kunal Pariani kpariani at
Wed Jan 7 23:37:22 UTC 2015

This is what i have. 

http { 
server { 
listen 443; 
location ^~ /zss 

Now as per, If you are running nginx as a proxy in front of An Amazon Web Services Elastic Load Balancer (ELB) which is the case for me, it is not safe to merely define an upstream using the hostname of ELB and call it a day. Although i don't want to use this resolver directive here and instead just want nginx to use the system DNS resolver (from /etc/resolv.conf). Is there a way to achieve this ? 


From: "Francis Daly" <francis at> 
To: nginx at 
Sent: Wednesday, January 7, 2015 3:14:17 PM 
Subject: Re: resolver directive doesn't fallback to the system DNS resolver 

On Mon, Jan 05, 2015 at 05:04:52PM -0600, Kunal Pariani wrote: 

Hi there, 

015/01/05 14:24:13 [error] 22560#0: *5 no resolver defined to resolve ... 

Seems like nginx is not falling back to the system DNS resolver in case the 'resolver' directive is not used. Isn't this incorrect behaviour ? 

events {} 
http { 
server { 
listen 8080; 
location /one { 

Works for me. 

What config file shows the problem that you report? 

(If the above fails for you, then it may be worth examining external parts.) 

Francis Daly francis at 

nginx mailing list 
nginx at 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list