Not clear regarding, " Also you might check using directly the hostname as
it might be possible that there is a bug when using variables."
I tried adding the variable for resolving the dns but still the ip address
does not changes. Is there any other way? or is there any bug in my script.
resolv
Sorry, backend1 its upstream in nginx configuration
upstream backend1 {
#ip of Apache back-end
server 192.168.0.1:8080;
}
2016-05-13 1:59 GMT+03:00 Alex Hall :
> Thanks! I followed you, until the proxy_pass. What is backend1, and where
> is it defined? I know it's something you made up, but h
Thanks! I followed you, until the proxy_pass. What is backend1, and where is it
defined? I know it's something you made up, but how does it know about Apache,
or Apache about it?
> On May 12, 2016, at 17:56, Yuriy Medvedev wrote:
>
> Hi, you can use vhost in Apache and configure proxy_pass in n
Hi, you can use vhost in Apache and configure proxy_pass in nginx
configuration
For apache2 somthing like that
ServerName foo.bar
DocumentRoot /home/sites/
Order deny,allow
Allow from all
ErrorLog /home/sites/logs/apache_error.log
CustomLog /home/sites/logs/apache_acce
Hello,
let Apache listen on a different port and create two server blocks in
nginx, one for each site. Then configure nginx to proxy the requests to sd2
to apache.
Just google "nginx reverse proxy" and you will find much information.
Yours sincerely
Sven Kirschbaum
2016-05-12 23:34 GMT+02:00 Ale
Hello all,
Here's what I'm trying to do. I have two sites, sd1.mysite.com and
sd2.mysite.com. The fun part is that sd1 is a Flask app, served by Nginx.
However, sd2 is OSTicket, which must be served by Apache, it seems. Of
course, Apache and Nginx can't listen to port 80 at the same time, and as
th
Hello!
On Thu, May 12, 2016 at 06:11:36AM -0400, RT.Nat wrote:
> I wanted check whether the resolver solves the DNS in a dynamic manner when
> the ip addresses changes.
>
> So I add the given code after several findings and yet the resolving the ip
> address is not happening.
>
> server{
>
Have you also checked that the DNS returns the correct value? As the
valid option means that nginx will ask the DNS server again, but if the
DNS replies with same old ip.. Also you might check using directly the
hostname as it might be possible that there is a bug when using variables.
Best re
I wanted check whether the resolver solves the DNS in a dynamic manner when
the ip addresses changes.
So I add the given code after several findings and yet the resolving the ip
address is not happening.
server{
...
resolver 8.8.8.8 valid=30s;
resolver_timeout 10s;
set $upstream "example
> Even adding the valid parameter the issue was not solved.
And what is the issue actually? Just saying "DNS caching issue"
and "problem" isn't really helpful.
___
nginx mailing list
nginx@nginx.org
http://mail
Even adding the valid parameter the issue was not solved.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,266857,266859#msg-266859
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
From Manual:
By default, nginx caches answers using the TTL value of a response. An
optional|valid|parameter allows overriding it:
resolver 127.0.0.1 [::1]:5353 valid=30s;
Before version 1.1.9, tuning of caching time was not possible, and
nginx always cached answers for the duration
Troubled up in DNS caching of the IP address for a given DNS name.
Adding the solution given below does not solve the problem of DNS caching in
NGINX.
resolver 8.8.8.8;
set $upstream_endpoint https://example.net:8080;
location / {
proxy_pass $upstream_endpoint;
}
Is there any solutions?
Po
13 matches
Mail list logo
