On 10/11/2018 07:57, Marco Davids (Private) wrote:
> Some of the name servers of irtf.org still seem to be serving that. But
> not all.
> Testing the NS-set gave:
[wrong paste - here's a better one]
for a in $(dig +nssearch +nodnssec +short irtf.org | awk '{print $11}');
do echo $a;dig irtf.org @$a|grep 20181109213626; done
65.22.7.1
20181109213626 20171109203628 46380 irtf.org.
65.22.9.1
20181109213626 20171109203628 46380 irtf.org.
65.22.8.1
20181109213626 20171109203628 46380 irtf.org.
2001:1900:3001:11::28
4.31.198.40
2a01:8840:7::1
20181109213626 20171109203628 46380 irtf.org.
2a01:8840:9::1
20181109213626 20171109203628 46380 irtf.org.
65.22.6.1
20181109213626 20171109203628 46380 irtf.org.
65.22.6.79
20181109213626 20171109203628 46380 irtf.org.
2a01:8840:6::1
20181109213626 20171109203628 46380 irtf.org.
2a01:8840:8::1
20181109213626 20171109203628 46380 irtf.org.
Only these two get it right:
2001:1900:3001:11::28
20191108202257 20181108192421 46380 irtf.org.
4.31.198.40
20191108202257 20181108192421 46380 irtf.org.
That's ns0.amsl.com (the primary?)
--
Marco
