Mailing List Archive

updates.spamassassin.org not resolving
Hi

updates.spamassassin.org is not resolving, tested with various
DNS systems. Can the admins please check ?

Kind Regards,
Andrew
Re: updates.spamassassin.org not resolving [ In reply to ]
Hi Andrew

dig + trace leads to primary DNS Server:

spamassassin.org. 3600 IN SOA ns2.pccc.com.
pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600

as published in the SOA record.

BUT:

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> ANY
updates.spamassassin.org @ns2.pccc.com. ;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3724
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

Looks that zone is NOT available on that primary DNS Server as my
request is being denied because it is 'recursive'.

Did they forget to pay? :-)

--
Mit freundlichen Grüssen

-Benoît Panizzon- @ HomeOffice und normal erreichbar
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
Re: updates.spamassassin.org not resolving [ In reply to ]
Let me take a look ASAP.

On Fri, Jul 23, 2021, 08:03 Benoît Panizzon <benoit.panizzon@imp.ch> wrote:

> Hi Andrew
>
> dig + trace leads to primary DNS Server:
>
> spamassassin.org. 3600 IN SOA ns2.pccc.com.
> pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600
>
> as published in the SOA record.
>
> BUT:
>
> ; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> ANY
> updates.spamassassin.org @ns2.pccc.com. ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3724
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
> ;; WARNING: recursion requested but not available
>
> Looks that zone is NOT available on that primary DNS Server as my
> request is being denied because it is 'recursive'.
>
> Did they forget to pay? :-)
>
> --
> Mit freundlichen Grüssen
>
> -Benoît Panizzon- @ HomeOffice und normal erreichbar
> --
> I m p r o W a r e A G - Leiter Commerce Kunden
> ______________________________________________________
>
> Zurlindenstrasse 29 Tel +41 61 826 93 00
> CH-4133 Pratteln Fax +41 61 826 93 01
> Schweiz Web http://www.imp.ch
> ______________________________________________________
>
Re: updates.spamassassin.org not resolving [ In reply to ]
TL;DR: Everything looks good to me.

I think you are just doing DNS calls that are either invalid or look like
you are trying to do discovery through recursion. For example:

dig -t txt 0.0.4.updates.spamassassin.org @ns2.pccc.com

;; ANSWER SECTION:
0.0.4.updates.spamassassin.org. 3600 IN CNAME
3.3.3.updates.spamassassin.org.
3.3.3.updates.spamassassin.org. 3600 IN TXT "1891700"

Try that specific dig which would be an example of a real dig needed for an
sa-update or something like an SOA pull, for example:

dig -t soa spamassassin.org @ns2.pccc.com

;; ANSWER SECTION:
spamassassin.org. 3600 IN SOA ns2.pccc.com.
pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600

Regards,
KAM
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Fri, Jul 23, 2021 at 8:26 AM Kevin A. McGrail <kmcgrail@apache.org>
wrote:

> Let me take a look ASAP.
>
> On Fri, Jul 23, 2021, 08:03 Benoît Panizzon <benoit.panizzon@imp.ch>
> wrote:
>
>> Hi Andrew
>>
>> dig + trace leads to primary DNS Server:
>>
>> spamassassin.org. 3600 IN SOA ns2.pccc.com.
>> pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600
>>
>> as published in the SOA record.
>>
>> BUT:
>>
>> ; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> ANY
>> updates.spamassassin.org @ns2.pccc.com. ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3724
>> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
>> ;; WARNING: recursion requested but not available
>>
>> Looks that zone is NOT available on that primary DNS Server as my
>> request is being denied because it is 'recursive'.
>>
>> Did they forget to pay? :-)
>>
>> --
>> Mit freundlichen Grüssen
>>
>> -Benoît Panizzon- @ HomeOffice und normal erreichbar
>> --
>> I m p r o W a r e A G - Leiter Commerce Kunden
>> ______________________________________________________
>>
>> Zurlindenstrasse 29 Tel +41 61 826 93 00
>> CH-4133 Pratteln Fax +41 61 826 93 01
>> Schweiz Web http://www.imp.ch
>> ______________________________________________________-
>>
>
Re: updates.spamassassin.org not resolving [ In reply to ]
On 23.07.21 13:58, Andrew Colin Kissa wrote:
>updates.spamassassin.org is not resolving, tested with various
>DNS systems. Can the admins please check ?

updates.spamassassin.org gives no data, because it's empty:

% dig any updates.spamassassin.org @b.auth-ns.sonic.net.

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> any updates.spamassassin.org @b.auth-ns.sonic.net.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18417
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;updates.spamassassin.org. IN ANY

;; AUTHORITY SECTION:
spamassassin.org. 3600 IN SOA ns2.pccc.com. pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600

;; Query time: 130 msec
;; SERVER: 184.173.92.18#53(184.173.92.18)


it has subdomains that do exist and have data tho.


--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"They say when you play that M$ CD backward you can hear satanic messages."
"That's nothing. If you play it forward it will install Windows."
Re: updates.spamassassin.org not resolving [ In reply to ]
> updates.spamassassin.org gives no data, because it's empty:

ouch, my bad. I would have expected NXDOMAIN for non existing, but just
an 'empty' reply, because it exists but does not contain any RR is
not what I expected. Then I tripped over the recursion warning.

--
Mit freundlichen Grüssen

-Benoît Panizzon- @ HomeOffice und normal erreichbar
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
Re: updates.spamassassin.org not resolving [ In reply to ]
My bad, actually thought updates.spamassassin.org was one of the mirrored-by
urls but it is sa-update.spamassassin.org

> On 23 Jul 2021, at 14:35, Kevin A. McGrail <kmcgrail@apache.org> wrote:
>
> TL;DR: Everything looks good to me.
Re: updates.spamassassin.org not resolving [ In reply to ]
On 2021-07-23 14:35, Kevin A. McGrail wrote:
> TL;DR: Everything looks good to me.

+1

> I think you are just doing DNS calls that are either invalid or look
> like you are trying to do discovery through recursion. For example:
>
> dig -t txt 0.0.4.updates.spamassassin.org [5] @ns2.pccc.com [2]

why is specific version needed ?, rules updates works imho with all
spamassassin versions if version is used in rule sets ?

> ;; ANSWER SECTION:
> 0.0.4.updates.spamassassin.org [5]. 3600 IN CNAME
> 3.3.3.updates.spamassassin.org [6].
> 3.3.3.updates.spamassassin.org [6]. 3600 IN TXT "1891700"

hope 0.0.4 comes out soon so all problems in dns can be solved :=)

still see the random dkim fails from fuglu while later testing in
spamc/spamd gives pass

dns test timeout not waiting for results ?

to low ttl on origin zone for dkim domain, i cant figure out why yet
Re: updates.spamassassin.org not resolving [ In reply to ]
On 2021-07-23 06:54, Benny Pedersen wrote:
> On 2021-07-23 14:35, Kevin A. McGrail wrote:
>> TL;DR: Everything looks good to me.
>
> +1
>
>> I think you are just doing DNS calls that are either invalid or look
>> like you are trying to do discovery through recursion.  For example:
>>
>> dig -t txt 0.0.4.updates.spamassassin.org [5] @ns2.pccc.com [2]
>
> why is specific version needed ?, rules updates works imho with all
> spamassassin versions if version is used in rule sets ?

Today that is true, but as ClamAV has discovered, old versions sometimes
behave badly in a way that can generate a lot of pain in the future.

Having requests already going to versioned URLs provides a lot of
options, for example, asking outdated versions to stay on outdated
rulesets:

0.2.3.updates.spamassassin.org. 3600 IN TXT "895075"

Which is better than feeding them a ruleset in a format that they won't
understand, and can't meaningfully use while the current release gets
new rulesets:

0.3.3.updates.spamassassin.org. 3600 IN TXT "1891700"