Define internaly DNS #1422

Closed
opened 2026-04-05 19:27:47 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @markusglaetzner on 6/1/2025

I have pangolin installed on a VPS. In my homelab I use Cosmos-Server as reverse proxy and docker-management. With Cosmos Server I have the advantage that I do not have to publish ports of my Docker applications (like treafik does). This means that in the homelab, I only can access my applications via the HTTPS domain defined in Cosmos Server (i.e., instead of "http://application:port" only "https://application.mydomain.org"). When I define access rules in pangolin in order to reach this "internal" service and use domain-names instead of ip-addresses and ports, pangolin tries to resolve this domain directly and gives me an error because this domain is not publicly accessible. The solution would be if I could specify internal DNS servers per service in pangolin.

*Originally created by @markusglaetzner on 6/1/2025* I have pangolin installed on a VPS. In my homelab I use Cosmos-Server as reverse proxy and docker-management. With Cosmos Server I have the advantage that I do not have to publish ports of my Docker applications (like treafik does). This means that in the homelab, I only can access my applications via the HTTPS domain defined in Cosmos Server (i.e., instead of "http://application:port" only "https://application.mydomain.org"). When I define access rules in pangolin in order to reach this "internal" service and use domain-names instead of ip-addresses and ports, pangolin tries to resolve this domain directly and gives me an error because this domain is not publicly accessible. The solution would be if I could specify internal DNS servers per service in pangolin.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1422