Hello!
On Thu, Dec 22, 2016 at 11:55:00AM -0500, ahamilton9 wrote:
> Almost. It was static group in the respect that it was dynamically grabbed
> on load, but the resolver just wasn't triggering at all after that.
>
> We did not have an explicit group defined, "php" literally referred to the
>
Almost. It was static group in the respect that it was dynamically grabbed
on load, but the resolver just wasn't triggering at all after that.
We did not have an explicit group defined, "php" literally referred to the
DNS name of the load balancer it was contacting. The rest of the domain was
bei
Hello!
On Wed, Dec 07, 2016 at 03:39:11PM -0500, ahamilton9 wrote:
> I've tried recreating the configuration on my local machine, and it works
> just fine. Really confusing. I don't understand why I get absolutely no DNS
> traffic on my nginx server (beyond the few calls from other services). Not
I've tried recreating the configuration on my local machine, and it works
just fine. Really confusing. I don't understand why I get absolutely no DNS
traffic on my nginx server (beyond the few calls from other services). Not a
single call from nginx.
Also, I read in the documentation that "By def
On Tue, Dec 06, 2016 at 12:43:50PM -0500, ahamilton9 wrote:
Hi there,
> 1) Does using a variable in fastcgi_pass actually allow the resolver to run,
> or is it just for proxy_pass as I've seen in 90% of examples?
Observation suggests "yes".
> 2) Is this configuration valid? It WORKS, but the re
I have an nginx server (1.10.1) configured that sends requests for PHP files
to our PHP tier by directing that traffic via fastcgi_pass to our PHP ELB
(AWS's Elastic Load Balancer). We occasionally get outages that a hard
stop/start of nginx solves, but are having trouble narrowing the issue down.
