| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
... and drop the racy code querying dns cache. ๐
|
|
|
|
|
|
The last one did not make it... Perhaps the cache just needs
a moment to settle?
|
|
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.
|
|
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? ๐คจ
|
|
|
|
|
|
... instead of else-branch.
This makes sure to skip hosts that just became "unknown".
(Possible soon!)
|
|
Just like we do everywhere else.
|
|
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.
|
|
|
|
|
|
|
|
... to use differing notification settings.
Add an origin name in netwatch configuration:
/tool/netwatch/add comment="notify, name=dns-google, origin=netwatch-notify-google" address=8.8.8.8;
/tool/netwatch/add comment="notify, name=dns-cloudflare, origin=netwatch-notify-cloudflare" address=1.1.1.1;
Then configure the notification settings in `global-config-overlay`:
:global EmailGeneralToOverride {
"netwatch-notify-google"="google@example.com";
"netwatch-notify-cloudflare"="cloudflare@example.com";
}
I think it is best to handle this as a hidden setting...
Handle with care!
|
|
... as global-functions depend on RouterOS 7.9beta already.
|
|
... now that in RouterOS 7.9 netwatch itself comes with a startup-delay.
Hosts in state 'unknown' are just ignored.
|
|
|
|
|
|
No functional change for the user... The migration is done
automatically.
|
Christian Hesse