netwatch-notify: work around race condition•••This used to crash every now and then with:
> script;error script error: no such item (4)
I guess this is caused by querying the dns cache just exactly when a
record expires. The chance is maximized: The script is started by
scheduler every minute, and the record's ttl is a multiple of a minute.
Let's query records that are not about to expire immediately, and
try again.
Christian Hesse
1
-8/+12
2024-02-28
netwatch-notify: restore the check ๐ฅด•••This reverts commit 28da1da49e275fef6089a103edf6c158bbff317f.
Chances are that we have to resolve a CNAME, that does not match when
querying the cache.
How to handle CNAME do multiple A records? ๐คจ
netwatch-notify: do not update with record in cache•••Using `:resolve` we have just one address, but chances are several
records do exist. These end up in cache, so we are happy to find them
there - no need to update then.
Christian Hesse