[GH-ISSUE #4351] Add Support for Hostnames in Access List via ngx_http_rdns_module #2793

New issue

Open

opened 2026-02-26 07:36:48 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:36:48 +03:00

Owner

Originally created by @emerysteele on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4351

Would be nice if you could add support for hostnames in the Access List via the ngx_http_rdns_module.

Some of my locations I need to be able to access from have dynamic IP addresses. But if this would added, I could use dynamic dns w/ a hostname to always have access, without having to open it up via HTTP auth.

Originally created by @emerysteele on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4351 Would be nice if you could add support for hostnames in the Access List via the ngx_http_rdns_module. Some of my locations I need to be able to access from have dynamic IP addresses. But if this would added, I could use dynamic dns w/ a hostname to always have access, without having to open it up via HTTP auth.

kerem added the

enhancement

stale

labels

2026-02-26 07:36:48 +03:00

kerem commented

2026-02-26 07:36:48 +03:00

Author

Owner

@vipergts450 commented on GitHub (Apr 7, 2025):

I just ran into a similar issue with NPM blocking access (403 Forbidden) from IPv6 LAN connections where the client is attempting to connect via it's dynamic IPv6 GUA instead of LAN ULA or fe80:: address. If NPM could resolve via rdns and subnet mask, I'm fairly certain it would work. Android clients especially prefer IPv6 over IPv4 for the last several years and seem to default to GUA for connection initiation.

The module suggested does not seem to be maintained anymore (maybe?), so I'm not sure about its stability or whether it's included anymore at all. I can't seem to find it in the docs/modules list.

@vipergts450 commented on GitHub (Apr 7, 2025): I just ran into a similar issue with NPM blocking access (403 Forbidden) from IPv6 LAN connections where the client is attempting to connect via it's dynamic IPv6 GUA instead of LAN ULA or fe80:: address. If NPM could resolve via rdns and subnet mask, I'm fairly certain it would work. Android clients especially prefer IPv6 over IPv4 for the last several years and seem to default to GUA for connection initiation. The module suggested does not seem to be maintained anymore (maybe?), so I'm not sure about its stability or whether it's included anymore at all. I can't seem to find it in the docs/modules list.

kerem commented

2026-02-26 07:36:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 20, 2025):

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

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

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#2793

No description provided.

Rows
Columns