john9527
Part of the Furniture
If you are doing all that already and handling all the update activity, there's no reason for you to call ddns_custom_updated at all. You can write a status file with the last address to /tmp (no nvram), and just make sure your scripts handles the case where the file isn't present as would occur during a reboot.OK, back to my complex DDNS script: While double NAT, I check external IP on my own. If external IP is the same as 30 minutes before, I know that since I saved previous value.
Now, nothing changed, I need not issue:
/sbin/ddns_custom_updated 1
as nothing changed. So, no point to update anything and write to NVRAM. Correct?