Re: www.irtf.org unreachable?

Lloyd Wood <lloyd.wood=40yahoo.co.uk@xxxxxxxxxxxxxx> · Sat, 10 Nov 2018 07:20:24 +0000 (UTC)

Thanks Marco - it's broken via the nameservers I use at
home and work, and has been for what, about a week?

So, denial of service of public content via an expired
certificate? Is this really what the web has come to? 

And who is responsible for and gets to fix it?

(redirecting from www.irtf.org to irtf.org is just
tricksy abuse for cosmetic purposes that doesn't help.)

L.

Lloyd Wood lloyd.wood@xxxxxxxxxxx http://about.me/lloydwood

________________________________
From: Marco Davids (Private) <mdavids=40forfun.net@xxxxxxxxxxxxxx>
To: ietf@xxxxxxxx 
Sent: Saturday, 10 November 2018, 11:57
Subject: Re: www.irtf.org unreachable?

On 10/11/2018 07:11, Dick Franks wrote:

> Just tried www.irtf.org and it appears to work for
> me  (UK, BT network)

Than perhaps you should ask BT to turn on DNSSEC-validation? ;-)

Although...

I noticed that for me 8.8.8.8 and 9.9.9.9 are serving an expired signature:

;; ANSWER SECTION:
irtf.org.    1509 IN    A 4.31.198.44
irtf.org.    1509 IN    RRSIG A 5 2 1800 (
            20191108202257 20181108192421 46380 irtf.org.
            DIYuuDXJH7sb1FhjhhSIr/1jn3dcUS1K8EqC6VeqCY7/
            OCo0tZpb30OwSRH82Y/KkHrR5UzKFtzFdEts5GSVoql5
            1RlCik6bSaa0OcuTdqKZuM1W6RhsxJncaBI/sV4i6JxQ
            ls2d50okfg4eHxIKMoa6WqqJ3jKnVMz2POQukO+sLUOf
            01kImGkTx0NQAp6fhNC9FweEQ6OnuqD/IIW+tHfKojSw
            ha6uZBgANXYHB8uDmHOzaP8SvAIfTlsvTaLElNaLxg1F
            4blO5GY45oonAXQxbqgarPXqrk6nnWTSCq1rBjyMNl9C
            tDlfKjHhedrSNgued4amJtW61WOPEfp+1g== )

Some of the name servers of irtf.org still seem to be serving that. But
not all.

1.1.1.1 had a newer one:

;; ANSWER SECTION:
irtf.org.    1390 IN    A 4.31.198.44
irtf.org.    1390 IN    RRSIG A 5 2 1800 (
            20191108202257 20181108192421 46380 irtf.org.
            DIYuuDXJH7sb1FhjhhSIr/1jn3dcUS1K8EqC6VeqCY7/
            OCo0tZpb30OwSRH82Y/KkHrR5UzKFtzFdEts5GSVoql5
            1RlCik6bSaa0OcuTdqKZuM1W6RhsxJncaBI/sV4i6JxQ
            ls2d50okfg4eHxIKMoa6WqqJ3jKnVMz2POQukO+sLUOf
            01kImGkTx0NQAp6fhNC9FweEQ6OnuqD/IIW+tHfKojSw
            ha6uZBgANXYHB8uDmHOzaP8SvAIfTlsvTaLElNaLxg1F
            4blO5GY45oonAXQxbqgarPXqrk6nnWTSCq1rBjyMNl9C
            tDlfKjHhedrSNgued4amJtW61WOPEfp+1g== )

Testing the NS-set gave:

for a in $(dig +nssearch +nodnssec +short irtf.org | awk '{print $11}');
do echo $a;dig irtf.org|grep 20181109213626; done
65.22.8.1
65.22.7.1
65.22.9.1
65.22.6.1
65.22.6.79
2001:1900:3001:11::28
2a01:8840:9::1
            20181109213626 20171109203628 46380 irtf.org.
4.31.198.40
2a01:8840:7::1
2a01:8840:6::1
2a01:8840:8::1
            20181109213626 20171109203628 46380 irtf.org.

--
Marco

> On Fri, 9 Nov 2018 at 23:36, Lloyd Wood
> <lloyd.wood=40yahoo.co.uk@xxxxxxxxxxxxxxx
> <mailto:40yahoo.co.uk@xxxxxxxxxxxxxx>> wrote:
> 
>     Is there any particular reason www.irtf.org <http://www.irtf.org>
>     appears
>     to be unreachable?
> 
>     (over IPv4. Haven't tried IPv6, which noone uses...)
> 
>     thanks
> 
>      Lloyd Wood lloyd.wood@xxxxxxxxxxx <mailto:lloyd.wood@xxxxxxxxxxx>

>    http://about.me/lloydwood
> 