Actions
Bug #16046
closed
Dynamic DNS IP address may not be updated after changing the interface of a Dynamic DNS entry
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
25.03
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
To reproduce:
- Configure two WANS, WAN1 and WAN2.
- Create a DDNS config using WAN1.
- Check that the domain now has WAN1's IP.
- Edit the DDNS config, change the interface to WAN2, then click
Save & Force Update. - Check that the domain now has WAN2's IP.
- Edit the DDNS config, change the interface to WAN1, then click
Save. - The domain still resolves to WAN1's IP.
To work around the issue, use Save & Force Update when changing the interface.
Updated by Marcos M 2 months ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Applied in changeset de695c0e4bd4e9b2bfb34ae2d557509865ccf9f5.
Updated by Jim Pingle about 2 months ago
- Subject changed from The DDNS IP address may not be updated after changing the configured DDNS interface to Dynamic DNS IP address may not be updated after changing the interface of a Dynamic DNS entry
Updated by Andrew Almond about 2 months ago
I opened redmine 16038 to address a similar issue of dynamic DNS IP addresses not updating due to caching.
Is it still necessary to cache dynamic DNS IP addresses? I know that rate limits used to be an issue with some providers, but that seems to be less of an issue now.
Maybe it makes sense to change the default behavior to 'forced' and users can disable that if necessary?
Updated by Marcos M about 2 months ago
Yes, and no. I've commented with more details on the relevant redmine.
Actions