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

[bug] IPs are cached by service instead domain name #79

Open
atesin opened this issue Dec 28, 2022 · 0 comments
Open

[bug] IPs are cached by service instead domain name #79

atesin opened this issue Dec 28, 2022 · 0 comments

Comments

@atesin
Copy link
Contributor

atesin commented Dec 28, 2022

hello... HEY... debugging another issue, i discovered ddupdate caches IPs by service, but i think it should be better cached by DOMAIN NAME instead... after all, IPs are bound to domain names actually, as logical

i think some people with multiple domains per services (like me) could have problems with this... what would happen currently, with services with multiple domains (and/or accounts) listening different connections?? ... it only caches IP from 1st domain?, from last?.... this could cause different domain updates overwriting cache each other, triggering them forever

(btw cache is located in ~/.cache/ddupdate/{service}.ip, it took me a couple hours to find out because is NOWHERE mentioned, even in logs=debug, neither show detected+cached ips to debug update process)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant