ddns-scripts: Remove minimum 5 minute wait

[brianjmurrell]

Maintainer: unclear by checking history of the package Makefile

Description:
To check if the update was successful.

Not all DDNS implementations have such huge latencies updating their services.

nsupdate for example, updates immediately and the update is immediately checkable.

Fixes: #20564

[brianjmurrell]

I don't think the CI failures are related to the nature of this PR. They look systememic.

[feckert]

My problem here is that if I merge this, then it could be that the DDNS no longer works for others, because they already had the wrong value before which is no longer fixed. I would therefore suggest that we use some kind of force that overrides the check.

[brianjmurrell]

My problem here is that if I merge this, then it could be that the DDNS no longer works for others, because they already had the wrong value before which is no longer fixed.

IMO, proper behaviour and bug fixing should never be avoided due to configurations relying on improper behaviour. Those broken configurations need to be fixed to work with proper values. IOW, any configuration that actually needs 5 minutes for the check needs to specify 5 minutes. Not 2 minutes, not 4 minutes, not 1 minute or even 30 seconds, etc.

I would therefore suggest that we use some kind of force that overrides the check.

So yet another option, perhaps, check_interval_minimum that defaults to the previously broken value of 300 seconds, but can be set lower, explicitly? Or a new, confusing, second check_interval_real perhaps that overrides check_interval?

[GeorgeSapkin]

@brianjmurrell still relevant? Commits needs to be squashed, PKG_RELEASE needs a bump and commit subject needs to start with a lowercase after the prefix.

[brianjmurrell]

@GeorgeSapkin Done. Thanks.

[feckert]

Thank you for your work.