On 2022-02-06 at 09:45:31 UTC-0500 (Sun, 6 Feb 2022 14:45:31 +)
Marc
is rumored to have said:
6.4.3.updates.spamassassin.org. 3600 IN CNAME
3.3.3.updates.spamassassin.org.
3.3.3.updates.spamassassin.org. 3600 IN TXT "1897787"
the "updates.spamassassin.org"
> >>
> >> 6.4.3.updates.spamassassin.org. 3600 IN CNAME
> >> 3.3.3.updates.spamassassin.org.
> >> 3.3.3.updates.spamassassin.org. 3600 IN TXT "1897787"
> >>
> >> the "updates.spamassassin.org" itself has no data.
>
> On 06.02.22 14:27, Marc wrote:
> >Oh ok, I did the dig because I got this
>
>[@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org
it resolves, but it does not resolve to A record dig searches for by
default:
6.4.3.updates.spamassassin.org. 3600 IN CNAME
3.3.3.updates.spamassassin.org.
3.3.3.updates.spamassassin.org. 3600 IN TXT "1897787"
the
> >[@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org
>
> it resolves, but it does not resolve to A record dig searches for by
> default:
>
> 6.4.3.updates.spamassassin.org. 3600 IN CNAME
> 3.3.3.updates.spamassassin.org.
> 3.3.3.updates.spamassassin.org. 3600 IN TXT "1897787"
>
> the
On 06.02.22 14:17, Marc wrote:
[@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org
it resolves, but it does not resolve to A record dig searches for by default:
6.4.3.updates.spamassassin.org. 3600 IN CNAME 3.3.3.updates.spamassassin.org.
3.3.3.updates.spamassassin.org. 3600 IN TXT
[@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org
[@svr ~]#
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 wrote:
>
> TL;DR: Everything looks good to me.
Hi
updates.spamassassin.org is not resolving, tested with various
DNS systems. Can the admins please check ?
Kind Regards,
Andrew
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
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
> 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
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
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
Let me take a look ASAP.
On Fri, Jul 23, 2021, 08:03 Benoît Panizzon wrote:
> Hi Andrew
>
> dig + trace leads to primary DNS Server:
>
> spamassassin.org. 3600IN SOA ns2.pccc.com.
> pmc.spamassassin.apache.org. 2021072305 7200 3600 604800 3600
>
> as published in the SOA
Hi Andrew
dig + trace leads to primary DNS Server:
spamassassin.org. 3600IN 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
15 matches
Mail list logo
