resolver directive doesn't fallback to the system DNS resolver

2015-01-05 Thread Kunal Pariani
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 th

Re: Use of Certs

2015-01-05 Thread Darren Pilgrim
On 12/29/2014 11:36 AM, Peter Fraser wrote: Hi All I am very new to nginx and am currently doing a lot of reading but would just love to have a nudge in the right direction I want to set up nginx as a reverse proxy for about three IIS servers behind a firewall. One of them is a public web server

Re: Location served by all virtual servers

2015-01-05 Thread Edho Arief
On Tue, Jan 6, 2015 at 3:47 AM, Styopa Semenukha wrote: > The hostname "domain1.com" is NOT matched by wildcard "*.domain1.com" (this > only matches subdomains), so it gets served by the default virtual host. Since > you don't have an explicit definiton of the default vhost, it's the first one > (

Re: Location served by all virtual servers

2015-01-05 Thread Styopa Semenukha
On Monday, January 05, 2015 01:11:08 PM blu wrote: > Hi, I have some configuration issue with my nginx. Currently both URLs > return the same page when I open: > http://domain1.com/SharedFIles and http://domain2.com/SharedFiles. > > Location "SharedFiles" is definied only in one virtual server (do

Location served by all virtual servers

2015-01-05 Thread blu
Hi, I have some configuration issue with my nginx. Currently both URLs return the same page when I open: http://domain1.com/SharedFIles and http://domain2.com/SharedFiles. Location "SharedFiles" is definied only in one virtual server (domain2) however it is accessible from both domains. How come?