Hello!
On Fri, Mar 03, 2017 at 04:53:56AM -0500, user384829 wrote:
> What about if we used a stream/tcp proxy_pass with resolver? Something like
> this:
>
> resolver 8.8.8.8 8.8.4.4 ipv6=off;
>
> stream {
> server {
> listen localhost:81;
> set $upstream_host my.upstream-host.com;
Hi Maxim,
Thanks for the reply.
What about if we used a stream/tcp proxy_pass with resolver? Something like
this:
resolver 8.8.8.8 8.8.4.4 ipv6=off;
stream {
server {
listen localhost:81;
set $upstream_host my.upstream-host.com;
proxy_pass $upstream_host:443;
}
}
server {
Hello!
On Wed, Mar 01, 2017 at 09:05:32AM -0500, user384829 wrote:
> OK thanks for the reply but how do I resolve this? Am I supposed to use
> upstream blocks with hostnames in them? My impression is that these won't be
> resolved inline with the TTL.
If you control your backends, consider using
Hi Maxim,
OK thanks for the reply but how do I resolve this? Am I supposed to use
upstream blocks with hostnames in them? My impression is that these won't be
resolved inline with the TTL.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,272679,272684#msg-272684
Hello!
On Wed, Mar 01, 2017 at 07:32:03AM -0500, user384829 wrote:
> Hi,
> I am wanting to resolve upstream hostnames used for proxy_pass inline with
> the TTL of the DNS record but when I add this configuration the response
> from nginx is MUCH slower.
> I've run tcpdump and the upstream DNS rec
Hi,
I am wanting to resolve upstream hostnames used for proxy_pass inline with
the TTL of the DNS record but when I add this configuration the response
from nginx is MUCH slower.
I've run tcpdump and the upstream DNS record is be resolved and reresolved
as TTL would dictate.
But requests are slower
