-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Log IP address that was sent to duckdns.org #72
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
We'll take that into consideration but in the meantime, duckdns website shows the last changed date for each subdomain when logged in. |
@aptalca - thank you for giving me hint for immediate chance to track my issue. I still think that having this also locally visible in my cluster would be nice. I could also run a job myself, but repeating same steps does not make much sense to me. |
We've made some enhancements to the container that take care of this one. Enjoy! |
Is this a new feature request?
Wanted change
I would like to be able to see IP address that was sent to duckdns.org in the log of the container. It would be fine to only add this extended logging upon setting of ENV variable (i.e.
EXTENDED_LOGING_ENABLED
) for extending logging.Reason for change
This would allow me to detect when the change of IP has happened and could relate it to small hiccups that are happening to instance of a service that I run in my network.
Proposed code change
change in
https://github.com/linuxserver/docker-duckdns/blob/master/root/app/duck.sh
I would provide PR to only log IPV4 or IPV6 or both based on configured option of
UPDATE_IP
variable.The text was updated successfully, but these errors were encountered: