When a router runs custom DDNS script under "Forced refresh interval (in days)" rule, how can said script differentiate that it is not a normal run but Forced refresh one?
Meaning: refresh external DDNS, no matter what you thing about it (refreshing it with the same data as before). Script by itself does the opposite: do not refresh external DDNS if there is no need for it. So, this is a special case I must handle.
There must be some counter or something script can check to recongize this situation.
Correct solution would be if a call to the script is made with additional parameter signifying forced refresh.
Meaning: refresh external DDNS, no matter what you thing about it (refreshing it with the same data as before). Script by itself does the opposite: do not refresh external DDNS if there is no need for it. So, this is a special case I must handle.
There must be some counter or something script can check to recongize this situation.
Correct solution would be if a call to the script is made with additional parameter signifying forced refresh.
My guess is that the call does not request forced explicitly.
