starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 09:55:51 +03:00

[GH-ISSUE #2423] IPv6 ULA creates problem in resolvers.conf #1699

New issue

Closed

opened 2026-02-26 07:32:06 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:32:06 +03:00

Owner

Originally created by @kingfisher77 on GitHub (Nov 23, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2423

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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.

Originally created by @kingfisher77 on GitHub (Nov 23, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2423  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker 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](https://github.com/robbertkl/docker-ipv6nat)) 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.

kerem

2026-02-26 07:32:06 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 4, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 4, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:32:06 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 21, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Mar 21, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1699

No description provided.

Rows
Columns