Hi everyone,
Our SpamAssassin rules have not gotten any recent updates (looks like
past 2 days). When investigating, sa-update tries to connect to:
2.4.3.updates.spamassassin.org
When doing a DNS lookup on this hostname it appears to be a CNAME which
points to: 3.3.3.updates.spamassassin.org. When doing a lookup for
3.3.3.updates.spamassassin.org it doesn't resolve, which I'm leaning
towards being the issue. Please see below lookup results:
---------------------------------------------------------------------
;; QUESTION SECTION:
;3.3.3.updates.spamassassin.org. IN A
;; AUTHORITY SECTION:
spamassassin.org. 1799 IN SOA ns2.pccc.com.
pmc.spamassassin.apache.org. 2020062505 7200 3600 604800 3600
;; Query time: 265 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Jun 26 10:10:28 SAST 2020
;; MSG SIZE rcvd: 131
---------------------------------------------------------------------
Anyone else seeing the same issue?
Thanks!
Stephan
Our SpamAssassin rules have not gotten any recent updates (looks like
past 2 days). When investigating, sa-update tries to connect to:
2.4.3.updates.spamassassin.org
When doing a DNS lookup on this hostname it appears to be a CNAME which
points to: 3.3.3.updates.spamassassin.org. When doing a lookup for
3.3.3.updates.spamassassin.org it doesn't resolve, which I'm leaning
towards being the issue. Please see below lookup results:
---------------------------------------------------------------------
;; QUESTION SECTION:
;3.3.3.updates.spamassassin.org. IN A
;; AUTHORITY SECTION:
spamassassin.org. 1799 IN SOA ns2.pccc.com.
pmc.spamassassin.apache.org. 2020062505 7200 3600 604800 3600
;; Query time: 265 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Jun 26 10:10:28 SAST 2020
;; MSG SIZE rcvd: 131
---------------------------------------------------------------------
Anyone else seeing the same issue?
Thanks!
Stephan