IPv6 ULA creates problem in resolvers.conf #2423
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes
- Are you sure you're not using someone else's docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
We use a dual stack IPv6-ULA/IPv4 custom docker network (together with ipv6 nat container)
This creates an unfortunate situation in /etc/nginx/conf.d/include/resolvers.conf (which is beeing generated from /etc/services.de/nginx/run)
This script generates an IPv6 dns entry in resolvers.conf which cannot resolve internal container service names, which leads to frequent server errors - when nginx randomly uses one of the IPv6 dns addresses for docker service name resolution.
Generated resolver.conf: resolver 127.0.0.11 [2001:4860:4860::8888] [2001:4860:4860::8844] valid=10s;
Nginx Proxy Manager Version
v2.9.19
Expected behavior
resolvers.conf should not have external ipv6 dns server addresses for internal docker service name resolution.
Screenshots
Operating System
Additional context
Not sure how to solve this one. Maybe another switch like "IPV6_RESOLVER=false"
We fixed this behaviour by linking a custom resolvers.conf without IPV6 addresses.
volumes:
- ./conf/resolvers.conf:/etc/nginx/conf.d/include/resolvers.conf:ro
$ cat conf/resolvers.conf
resolver 127.0.0.11 valid=10s;
No errors anymore.