Support "Domain" for Resource Access Allowlisting #129

Closed
opened 2025-11-13 11:50:50 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @gokussjx on GitHub (Mar 9, 2025).

Resource access allowlisting currently looks like this:

Image

This is great for static IP, however, this cannot work for systems with a dynamic IP address.
Adding support for a "Domain" would be very beneficial.

The use-case I'm thinking of is for self-hosted services which have a dynamic IP address, often bound with dynamic DNS services such as DynDNS, DuckDNS, etc. Since the host requests the upstream DNS to update the IP address, all Pangolin has to do is query it on the fly and allow that IP access. One potential implementation around the TTL is to cache the old IP for a short period of time.

Originally created by @gokussjx on GitHub (Mar 9, 2025). Resource access allowlisting currently looks like this: ![Image](https://github.com/user-attachments/assets/1c637f67-4f7f-4319-aecd-61cb378e8b0a) This is great for static IP, however, this cannot work for systems with a dynamic IP address. Adding support for a "Domain" would be very beneficial. The use-case I'm thinking of is for self-hosted services which have a dynamic IP address, often bound with dynamic DNS services such as DynDNS, DuckDNS, etc. Since the host requests the upstream DNS to update the IP address, all Pangolin has to do is query it on the fly and allow that IP access. One potential implementation around the TTL is to cache the old IP for a short period of time.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#129