4 Commits

Author SHA1 Message Date
Varun Gupta
7b09fefd17 Update configs for active hosts only on ddns update
Other changes:
- Fixed null property read error on clients (when switching to public access)
- Use separate `resolvedAddress` field for resolved IP instead of overwriting address
- Reduced ddns log verbosity
2024-04-28 18:00:23 -07:00
Varun Gupta
743cdd8b0b Eliminate circular dependency 2024-04-28 18:00:23 -07:00
Varun Gupta
ec9eb0dd60 Refactor and integrate ddns resolution with nginx module
Refactored ddns resolver so that no patching is done. nginx.js will automatically resolve ddns addresses if needed.

Added dedicated logger scope for ddns resovler.
2024-04-28 18:00:04 -07:00
Varun Gupta
5586709d03 Initial pass at DDNS support for client addresses
This is a first pass attempt at adding support for using ddns (really any resolvable domain name) as the address in access list clients.

This helps make it possible to restrict access to hosts using a dynamic public IP (e.g. allow access to a proxied host from your local network only via ddns address).

Current approach is hacky since it was developed by manually replacing files in an existing npm docker container. Future commits will integrate this better and avoid needing to patch/intercept existing APIs.

See associated PR for more details.
2024-04-28 17:58:58 -07:00