resolver directive doesn't fallback to the system DNS resolver

[Kunal Pariani]

This is what i have. 

http { 
server { 
listen 443; 
location ^~ /zss 
{ 
proxy_pass https://www.example.com$request_uri; 
} 
} 
} 

Now as per http://gc-taylor.com/blog/2011/11/10/nginx-aws-elb-name-resolution-resolvers/, 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 ? 

Thanks 
-Kunal 


From: "Francis Daly" <francis at daoine.org> 
To: nginx at nginx.org 
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 { 
proxy_pass http://www.example.com; 
} 
} 
} 
== 

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.) 

f 
-- 
Francis Daly francis at daoine.org 

_______________________________________________ 
nginx mailing list 
nginx at nginx.org 
http://mailman.nginx.org/mailman/listinfo/nginx 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150107/532d2c24/attachment.html>