You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sysadmins@spamassassin.apache.org by Bill Cole <bi...@apache.org> on 2019/01/07 21:42:07 UTC

DNS is broken for spamassassin.org

The last SVN commit has a SOA serial of 2019010505 and it looks good, 
but ns2.ena.com and ns2.pccc.com are both saying the serial is 
2019010705 and nothing in the zone resolves.


Re: DNS is broken for spamassassin.org

Posted by Bill Cole <bi...@apache.org>.
On 7 Jan 2019, at 17:09, Kevin A. McGrail wrote:

> Interesting. I show a zone transfer:
>
> Jan  7 04:30:00 ns2 named[2465]: zone spamassassin.org/IN: 
> transferred
> serial 2019010705
> Jan  7 04:30:00 ns2 named[2465]: transfer of 'spamassassin.org/IN' 
> from
> 62.210.60.231#53: Transfer completed: 4 messages, 117 records, 6716
> bytes, 0.277 secs (24245 bytes/sec)
>
> And data in the zone.
>
> But I agree it's acting odd.  These errors look odd to me and a dig 
> -t
> any isn't  coming back.


Well, that isn't necessary bad. There's a very strong argument against 
answering ANY queries, and I hope it's off on ns2.

ALSO: now everything is looking fine. The queries I got noanswer/noerror 
responses for circa 20:00 UTC now are working.  I pulled a txt version 
of the zone from pdns on sa-vm1 and its only differences with the zone 
in SVN are the serial number and the TXT value of the last rev, which 
matches this morning's update.

Gremlins...

>
> Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) 
> resolving
> 'spamasssassin.org/SOA/IN': 2001:500:12::d0d#53
> Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) 
> resolving
> 'spamasssassin.org/SOA/IN': 2001:dc3::35#53
> Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) 
> resolving
> 'spamasssassin.org/SOA/IN': 2001:500:48::1#53
> Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) 
> resolving
> 'spamasssassin.org/SOA/IN': 2001:500:b::1#53
> Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) 
> resolving
> 'spamasssassin.org/SOA/IN': 2001:500:e::1#53
> Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) 
> resolving
> 'spamasssassin.org/SOA/IN': 2001:500:c::1#53
>
> Dave, any ideas?
>
> On 1/7/2019 4:42 PM, Bill Cole wrote:
>> The last SVN commit has a SOA serial of 2019010505 and it looks good,
>> but ns2.ena.com and ns2.pccc.com are both saying the serial is
>> 2019010705 and nothing in the zone resolves.
>
>
> -- 
> *Kevin A. McGrail*
> CEO Emeritus
>
> Peregrine Computer Consultants Corporation
> 10311 Cascade Lane
> Fairfax, VA 22032
>
> http://www.pccc.com/
>
> 703-359-9700 / 800-823-8402 (Toll-Free)
> 703-798-0171 (wireless)
> KMcGrail@PCCC.com <ma...@pccc.com>
>
> https://www.linkedin.com/in/kmcgrail


-- 
Bill Cole

Re: DNS is broken for spamassassin.org

Posted by "Kevin A. McGrail" <KM...@PCCC.com>.
Interesting. I show a zone transfer:

Jan  7 04:30:00 ns2 named[2465]: zone spamassassin.org/IN: transferred
serial 2019010705
Jan  7 04:30:00 ns2 named[2465]: transfer of 'spamassassin.org/IN' from
62.210.60.231#53: Transfer completed: 4 messages, 117 records, 6716
bytes, 0.277 secs (24245 bytes/sec)

And data in the zone.

But I agree it's acting odd.  These errors look odd to me and a dig -t
any isn't  coming back.

Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) resolving
'spamasssassin.org/SOA/IN': 2001:500:12::d0d#53
Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) resolving
'spamasssassin.org/SOA/IN': 2001:dc3::35#53
Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) resolving
'spamasssassin.org/SOA/IN': 2001:500:48::1#53
Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) resolving
'spamasssassin.org/SOA/IN': 2001:500:b::1#53
Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) resolving
'spamasssassin.org/SOA/IN': 2001:500:e::1#53
Jan  7 22:06:27 ns2 named[2465]: error (network unreachable) resolving
'spamasssassin.org/SOA/IN': 2001:500:c::1#53

Dave, any ideas?

On 1/7/2019 4:42 PM, Bill Cole wrote:
> The last SVN commit has a SOA serial of 2019010505 and it looks good,
> but ns2.ena.com and ns2.pccc.com are both saying the serial is
> 2019010705 and nothing in the zone resolves.


-- 
*Kevin A. McGrail*
CEO Emeritus

Peregrine Computer Consultants Corporation
10311 Cascade Lane
Fairfax, VA 22032

http://www.pccc.com/

703-359-9700 / 800-823-8402 (Toll-Free)
703-798-0171 (wireless)
KMcGrail@PCCC.com <ma...@pccc.com>

https://www.linkedin.com/in/kmcgrail