starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #167] Multi-level subdomain #147

New issue

Closed

opened 2026-02-26 06:30:46 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:30:46 +03:00

Owner

Originally created by @mskenderian-wps on GitHub (Jul 13, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/167

setup a new proxy host.
nvr.fulton.example.com

going to that link it wont find the host.
i added nvr.example.com to the same host.
going to this link works fine.

do we not support multilevel subdomains?

Originally created by @mskenderian-wps on GitHub (Jul 13, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/167 setup a new proxy host. nvr.fulton.example.com going to that link it wont find the host. i added nvr.example.com to the same host. going to this link works fine. do we not support multilevel subdomains?

kerem

2026-02-26 06:30:46 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:30:47 +03:00

Author

Owner

@der--flo commented on GitHub (Jul 17, 2019):

I'm using a lot of 4th level domains in nginx-proxy-manager without problems...

@der--flo commented on GitHub (Jul 17, 2019): I'm using a lot of 4th level domains in nginx-proxy-manager without problems...

kerem commented

2026-02-26 06:30:47 +03:00

Author

Owner

@jc21 commented on GitHub (Jul 23, 2019):

This is just a wrapper for Nginx so it will do whatever nginx allows, I too am using something.somehere.mydomain.com just fine. My guess is that your DNS is not correctly configured for the FQDN.

@jc21 commented on GitHub (Jul 23, 2019): This is just a wrapper for Nginx so it will do whatever nginx allows, I too am using `something.somehere.mydomain.com` just fine. My guess is that your DNS is not correctly configured for the FQDN.

kerem commented

2026-02-26 06:30:47 +03:00

Author

Owner

@mskenderian-wps commented on GitHub (Jul 29, 2019):

I setup a new instance and it seems to be working.

@mskenderian-wps commented on GitHub (Jul 29, 2019): I setup a new instance and it seems to be working.

kerem commented

2026-02-26 06:30:47 +03:00

Author

Owner

@BoguschMedia commented on GitHub (Mar 24, 2024):

For those who have been searching for a solution to a similar problem, here's a bit of info (specific on my problem, but i hope it will help someone ;-) ):

I encountered problems with NPM using multi-level subdomains. However, it turns out the issue isn't with NPM itself; it's the classic "it's always DNS" scenario. It seems that some DNS servers provided by my local internet service are having trouble with multi-level subdomains (for reasons unknown).

Furthermore, it appears that propagating DNS entries worldwide is a bit slower compared to standard (sub-)domains, which have only one level, so to speak.

To make matters worse, I've found many issues related to DNS in German router forums, which can be traced back to the use of Fritz!Box routers. It seems that these devices occasionally suffer from bugs.

I personally experienced a problem where, even after several days, my DNS from the internet provider "EWEtel" did not correctly output the DNS entries. Additionally, my Fritz!Box seemed to distort the response from the DNS server of EWE (and others).

So, if you can't reach a subdomain or multi-level subdomain, try to troubleshoot your DNS using tools like nslookup or online services such as dnschecker.org.

@BoguschMedia commented on GitHub (Mar 24, 2024): **For those who have been searching for a solution to a similar problem, here's a bit of info (specific on my problem, but i hope it will help someone ;-) ):** I encountered problems with NPM using multi-level subdomains. However, it turns out the issue isn't with NPM itself; it's the classic "**it's always DNS**" scenario. It seems that some DNS servers provided by my local internet service are having trouble with multi-level subdomains (for reasons unknown). Furthermore, **it appears** that propagating DNS entries worldwide is a bit slower compared to standard (sub-)domains, which have only one level, so to speak. To make matters worse, I've found many issues related to DNS in German router forums, which can be traced back to the use of Fritz!Box routers. It seems that these devices occasionally suffer from bugs. I personally experienced a problem where, even after several days, my DNS from the internet provider "EWEtel" did not correctly output the DNS entries. Additionally, my Fritz!Box seemed to distort the response from the DNS server of EWE (and others). **So, if you can't reach a subdomain or multi-level subdomain, try to troubleshoot your DNS using tools like nslookup or online services such as [dnschecker.org](https://dnschecker.org/).**

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

No description provided.

Rows
Columns