Open pszypowicz opened 2 years ago
I have a CNAME set up, and it works fine. Do you have a valid entry in NPM that would resolve to your sub1.domain.com and would be accessible from the same location where you NPM is residing?
What DNS server is in /data/nginx/resolvers.conf I think this is made at first start and if you have changed DNS servers since perhaps that needs updating. i.e. the NPM container and the Nginx may use different DNS servers for the lookup giving you the differing results you are seeing. The container (/etc/resolv.conf) probably uses 127.0.0.11 so points to the docker service which combines both docker hosted container names and forwards to the host to lookup requests external to docker.
I found some time to reproduce the problem again and investigate it deeper.
I do not have /data/nginx/resolvers.con
file, but I found that file in /etc/nginx/conf.d/include
and it looks like this
[root@docker-7e906569418d:/etc/nginx/conf.d/include]# cat resolvers.conf
resolver 127.0.0.11 valid=10s;
[root@docker-7e906569418d:/etc/nginx/conf.d/include]# cat /etc/resolv.conf
nameserver 127.0.0.11
options ndots:0
So it looks like they both use the same dns server?
Issue is now considered stale. If you want to keep it open, please comment :+1:
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
I have 2 entries in my dns server: sub1.domain.com -> CNAME sub2.domain.com sub2.domain.com -> A record 192.168.0.2
I can get IP's of both from the shell of NPM container:
I'm configuring Proxy Host.
When I will configure destination to point to sub2.domain.com, everything works.
But when I'm using sub1.domain.com I see following error in the error_log:
Nginx Proxy Manager Version
v2.9.18
To Reproduce Steps to reproduce the behavior:
Host not found
Expected behavior
Site should work
Operating System
Synology docker
Additional context
DNS is handled with Adguard
DNS rewrites