kunalvjti Wrote:
---
Is there already a patch for this ?
I am not completely sure of how to make the nginx resolver (in
ngx_resolver.c) fallback to libresolv automatically and if this not
Have a look at a Lua solution, not everything works
suggestions ?
Thanks
-Kunal
- Original Message -
From: Yichun Zhang (agentzh) agen...@gmail.com
To: nginx@nginx.org
Sent: Wednesday, January 7, 2015 4:30:06 PM
Subject: Re: resolver directive doesn't fallback to the system DNS resolver
Hello!
On Wed, Jan 7, 2015 at 4:15 PM, Francis Daly wrote
Hello!
On Mon, Jan 12, 2015 at 1:48 PM, Kunal Pariani wrote:
Is there already a patch for this ?
AFAIK, the Tengine fork has a patch for this.
I am not completely sure of how to make the nginx resolver (in
ngx_resolver.c) fallback to libresolv automatically and if this not trivial
enough,
Thanks Yichun Zhang..
- Original Message -
From: Yichun Zhang (agentzh) agen...@gmail.com
To: nginx@nginx.org
Sent: Monday, January 12, 2015 2:19:08 PM
Subject: Re: resolver directive doesn't fallback to the system DNS resolver
Hello!
On Mon, Jan 12, 2015 at 1:48 PM, Kunal Pariani wrote
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 ?
). Is there a way to achieve this ?
Thanks
-Kunal
From: Francis Daly fran...@daoine.org
To: nginx@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
On Wed, Jan 07, 2015 at 05:37:22PM -0600, Kunal Pariani wrote:
Hi there,
http {
server {
listen 443;
location ^~ /zss
{
proxy_pass https://www.example.com$request_uri;
}
}
}
Ok, I see the no resolver defined to resolve www.example.com message
when I make a request that matches
Hello!
On Wed, Jan 7, 2015 at 4:15 PM, Francis Daly wrote:
(You could probably come up with a way to read /etc/resolv.conf when it
changes, and update the nginx config and reload it; but that's a dynamic
reconfiguration problem, not an nginx dynamic reconfiguration problem.)
Yeah, I think
Ping..
Thanks
-Kunal
From: Kunal Pariani kpari...@zimbra.com
To: nginx@nginx.org
Sent: Monday, January 5, 2015 3:04:52 PM
Subject: resolver directive doesn't fallback to the system DNS resolver
Hello,
I am looking at how to use nginx's resolver directive
(http://nginx.org/en/docs/http
Hello,
I am looking at how to use nginx's resolver directive
(http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver) to address
this one issue i am facing. I have a host for which there is already an entry
in the system DNS resolver (verified using nslookup/dig) but when i specify
10 matches
Mail list logo
