Bug #3901
closed
DynDNS is not forcefully updated after powerup
0%
Description
Hi
I was playing around with two instances of pfSense (with the same config).
pfSense1 had IP a.b.c.x (via DHCP) and was shut down.
pfSense2 got IP a.b.c.y (via DHCP) and was in use for a few hours (I copied a backuped config of pfSense1 and it then updated DynDNS)
When I powered up pfSense1 again which got again IP a.b.c.x (via DHCP) - it didn't update the DynDNS records because it didn't realize the change of IP.
Therefore I'd suggest to always update DynDNS after a powerup.
Regards & Thank you
Updated by Chris Buechler over 9 years ago
- Status changed from New to Rejected
You'll see in the system log how it works. If your IP hasn't changed, and it's been less than 25 days since the last update, it skips the update. I went through and tested all this on 2.2 to verify that's still all working correctly, and it is. There is no need to force an update.
Updated by Philippe Schnyder over 9 years ago
From my point of view the current behaviour is not perfect.
As I described above it might be the case that the data saved at the DynDNS provider might have been changed while the device was powered off (in my case because I used a second pfSense installation with the same settings which was assigned an other IP). Therefore I'd prefer to have all DynDNS settings updated after a reboot.
Updated by Chris Buechler over 9 years ago
that's a scenario that no client accounts for. Excessive updating can get you banned from some of the providers, which is why the current behavior is proper. You shouldn't re-use DynDNS names as there are tons of possibilities for messing them up in that case, and where you do, you'll have to take additional precautions and possibly force updates at times (which you can do manually, or you can throw in a script to do the same at boot). If you'd like to discuss further, please post to the forum or mailing list.