Hello,
I
'm trying to use Caddy to filter access for some websites.
I want to resolve my website with remote_ip but with my dyndns is resolve (because my home ip is changing).
Yeah, the remote_ip matcher is meant for IP addresses, not domain names, as its name would imply.
If you want a matcher that does DNS lookups, you’ll need to implement it yourself, as there’s nothing that could do that in vanilla Caddy:
But I’m not sure that what you’re trying to do makes sense. The remote_ip matcher looks at the IP address of the first-immediate client that’s connecting to your server.
If you want a matcher that does DNS lookups, you’ll need to implement it yourself, as there’s nothing that could do that in vanilla Caddy
I’m not a pro of go, but I will try to do it. But for me, it’s a missing feature from remote_ip because for many clients their home IPs change frequently.
The use case is here, is to access to a remote website from my home. But my home IP change frequently so I want to resolve ip with dyndns entry.
I think you’d be better off using authentication for this, instead of relying on the remote IP. Use the basicauth directive, or you could set up Authelia with the forward_auth directive.