> Am 14.03.2019 um 05:17 schrieb root <[email protected]>: > > Fetching sa-update URLs from > http://spamassassin.apache.org/updates/MIRRORED.BY > > http://sa-update.dnswl.org/ (78.47.167.123): DOWN
Interesting, it seems this script is (sometimes?) picking up the A record which should have been gone from DNS cache: # dig +trace -t a sa-update.dnswl.org <http://sa-update.dnswl.org/> (…) sa-update.dnswl.org. 21600 IN A 116.203.4.105 # dig +trace -t soa dnswl.org <http://dnswl.org/> dnswl.org. 21600 IN SOA zone-ns1.dnswl.org. admins.dnswl.org. 1903112142 3600 1200 302400 21600 „1903112142“ is 2019-03-11 21:42 (in CET), ie three days ago. I see that the old IP 78.47.167.123 only appeared every few hours (taken from the Date: headers in the past few mails): Date: Thu, 14 Mar 2019 04:17:05 +0000 (UTC) Date: Wed, 13 Mar 2019 19:18:07 +0000 (UTC) Date: Wed, 13 Mar 2019 17:18:06 +0000 (UTC) Date: Wed, 13 Mar 2019 14:17:24 +0000 (UTC) Date: Wed, 13 Mar 2019 12:17:06 +0000 (UTC) Is it a DNS issue on sa-vm1, or is it something I overlooked on our end? — Matthias
