Resolver directive not working?

Checklist

• Please read the setup instructions
• Please read the FAQ

What is troubling you?

I’m using proxy manager to proxy docker containers but when a container is restarted the proxy manager reports a 502 BAD GATEWAY. I tried adding the resolver directive in the advanced configuration, like resolver 127.0.0.11 ipv6=off valid=30s; but it doesn’t seem to work:

Do I need to use a variable for the resolve to work properly?

[chaptergy]

I’m pretty sure he means like this:

location / {
    resolver 127.0.0.11 valid=30s;
    set $custom_upstream example.com;
    proxy_pass http://$custom_upstream:80;
}

The $custom_upstream is the variable which will prevent DNS resolution at startup.

Which you can paste into your advanced tab.

[rlogiacco]

I managed to have it working and it also solves #633 : you must use a variable and the resolver directive. The variable prevents the DNS resolution at boot from nginx, the resolver determines how frequently such variable is checked against the internal docket DNS.