jackdlail
Occasional Visitor
I want to use a public domain name with some docker containers on a NAS with nginx proxy manager so they can have SSL, too,
I got a domain at Cloudflare, and created subdomains for my Docker apps, all pointing to the internal IP of my NAS (instead of the public IP of the router). While a hack, with ports 80 and 443 closed, it hopefully limits the domains to internal use only.
My issue is nothing inside my local LAN resolves those domains even though I can see they have propogated worldwide with websites that check that. Why doesn't the 192.168.50.165.xxx address resolve to my subdomain names that use that IP in their A records?
If I add the addresses to my hosts file, they resolve for that machine, but that's not what I want.
Is this expected behavior or is there some setting I need to change?
I am using a ZenWiFi XT 8 router system running stock ASUS software on the latest firmware.
The NAS is a QNAP.
The A records for the subdomains are not proxied by Cloudflare.
I got a domain at Cloudflare, and created subdomains for my Docker apps, all pointing to the internal IP of my NAS (instead of the public IP of the router). While a hack, with ports 80 and 443 closed, it hopefully limits the domains to internal use only.
My issue is nothing inside my local LAN resolves those domains even though I can see they have propogated worldwide with websites that check that. Why doesn't the 192.168.50.165.xxx address resolve to my subdomain names that use that IP in their A records?
If I add the addresses to my hosts file, they resolve for that machine, but that's not what I want.
Is this expected behavior or is there some setting I need to change?
I am using a ZenWiFi XT 8 router system running stock ASUS software on the latest firmware.
The NAS is a QNAP.
The A records for the subdomains are not proxied by Cloudflare.