You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there.
First of thanks for this wonderful software. I've been desperately needing exactly this.
Anyways, what I would love to have is (an optional) way for the service to start cleaning up old entries. To give them a TTL for their existance. (Please don't use the TTL value for that. It should be a different one)
The main reason I'm asking for this is quite simple. We use this to identify devices. They all get their own unique ID and that's how we address them. Now the setup they are a part of is very volatile. Meaning that IP addresses get reassigned often. And devices get added and removed from the pool frequently too. This means that for a device that has been removed from the pool could still have a DNS entry. And a new device might have gotten that IP. So then instead of getting an error that the name cannot be resolved, we would connect to the wrong device without even knowing really.
I hope that request makes sense to you. And I also hope that it won't be too much work to implement.
The text was updated successfully, but these errors were encountered:
Hey, thanks for your feedback. The idea makes sense to me and I actually have a similar use-case for this. However, unfortunately I've been quite busy recently and I don't know when I will be able to implement this. If anyone would like to file a MR, I'd highly appreciate it.
I've implemented this feature and there's an open PR for it. In the mean time you (while it is not merged here) you can build it from my fork: https://github.com/sgyurko/docker-ddns
Hi there.
First of thanks for this wonderful software. I've been desperately needing exactly this.
Anyways, what I would love to have is (an optional) way for the service to start cleaning up old entries. To give them a TTL for their existance. (Please don't use the TTL value for that. It should be a different one)
The main reason I'm asking for this is quite simple. We use this to identify devices. They all get their own unique ID and that's how we address them. Now the setup they are a part of is very volatile. Meaning that IP addresses get reassigned often. And devices get added and removed from the pool frequently too. This means that for a device that has been removed from the pool could still have a DNS entry. And a new device might have gotten that IP. So then instead of getting an error that the name cannot be resolved, we would connect to the wrong device without even knowing really.
I hope that request makes sense to you. And I also hope that it won't be too much work to implement.
The text was updated successfully, but these errors were encountered: