Skip to content
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

Timeout the pubIp env variable set in container #11

Closed
navilg opened this issue Mar 10, 2024 · 0 comments · Fixed by #15
Closed

Timeout the pubIp env variable set in container #11

navilg opened this issue Mar 10, 2024 · 0 comments · Fixed by #15
Assignees
Labels
enhancement New feature or request

Comments

@navilg
Copy link
Owner

navilg commented Mar 10, 2024

Currently when IP address is set in namecheap, ncddns sets an env variable in current container so that it can compare the next time with current public IP. It prints the message "DNS record is same as current IP" if current public IP and env variable set is same.

This may not work if someone changes the IP address of a dns from namecheap dashboard unless container is restarted again. To avoid this, We can have a timeout set for env variable set, after which it should be wiped out so that fresh attempt to add ip address is made by ncddns.

@navilg navilg added the enhancement New feature or request label Mar 10, 2024
@navilg navilg self-assigned this Mar 10, 2024
navilg added a commit that referenced this issue Sep 8, 2024
Signed-off-by: Navratan Lal Gupta <navilg0409@gmail.com>
navilg added a commit that referenced this issue Sep 8, 2024
…set-in-container

#11 timeout the pubip env variable set in container
@navilg navilg linked a pull request Sep 8, 2024 that will close this issue
@navilg navilg closed this as completed in #15 Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant