You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I've recently enabled IPv6 on my docker environment and since then I get intermittent 502 errors on my sites. Digging into it, I found out that /etc/nginx/conf.d/include/resolvers.conf was being auto-populated with the docker v4 dns server plus two public ipv6 resolvers. Once I mounted my own resolvers.conf (read-only) file with just the docker v4 dns everything went back to normal. I know that I could go through and add the resolver line in the advance config of each host but that's a pain.
Describe the solution you'd like
I suggest the default be the docker v4 dns server. That seems like the solution most people would want. If not, maybe a global setting to override the default resolver.
Describe alternatives you've considered
I mounted my own resolvers.conf file over the default; read-only so that NPM can't re-write it. I could also add my resolver config line to each host in the advance section but that would be a pain.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I've recently enabled IPv6 on my docker environment and since then I get intermittent 502 errors on my sites. Digging into it, I found out that /etc/nginx/conf.d/include/resolvers.conf was being auto-populated with the docker v4 dns server plus two public ipv6 resolvers. Once I mounted my own resolvers.conf (read-only) file with just the docker v4 dns everything went back to normal. I know that I could go through and add the resolver line in the advance config of each host but that's a pain.
Before:
resolver 127.0.0.11 [2001:4860:4860::8888] [2001:4860:4860::8844] valid=10s;
After:
resolver 127.0.0.11 valid=10s;
Describe the solution you'd like
I suggest the default be the docker v4 dns server. That seems like the solution most people would want. If not, maybe a global setting to override the default resolver.
Describe alternatives you've considered
I mounted my own resolvers.conf file over the default; read-only so that NPM can't re-write it. I could also add my resolver config line to each host in the advance section but that would be a pain.
Additional context
N/A
The text was updated successfully, but these errors were encountered: