Unfortunately, that's based on the list of name servers in the authoritative zone file and not based on the list of servers in effect as set by the dot org registry. I've expanded on Tom's script to take that into account and found there's apparently a couple of servers not answering at all. $ cat nssoa.sh #!/bin/bash ZONE=${1:-ampr.org} PARENTDOMAIN=$(echo -n $ZONE | cut -d'.' -f 2-) REGISTRYNS=$(dig -t ns +short $PARENTDOMAIN | tail -n1) for nameserver in $(dig +norecurse +authority +noadditional @$REGISTRYNS $ZONE | grep -i ^$ZONE | cut -f 6); do echo "$(dig +short soa @$nameserver $ZONE | cut -d' ' -f3)" "$nameserver" done $ ./nssoa.sh | sort dig: couldn't get address for 'ns.nonanet.net.uk.': not found 1708281715 ns1.defaultroute.net. 1708282030 munnari.oz.au. 1708291800 ampr-dns.in-berlin.de. 1708291800 ampr.org. 1708291800 ns2.threshinc.com. ns.nonanet.net.uk. timed hamradio.ucsd.edu. On Tue, Aug 29, 2017 at 11:55 AM, Brian Kantor <Brian(a)ucsd.edu> wrote:

Yes, I'm now aware that there are nameservice problems and I'm working on it. It won't be fixed quickly because it requires manual intervention by several people in many different places around the globe, including the registries. Thanks all for bringing this to my attention. - Brian On Tue, Aug 29, 2017 at 04:03:47PM -0500, Scott Nelson wrote: > A good source of diagnostic information is IntoDNS, and that shows a lot of problems with ampr.org: > > https://intodns.com/ampr.org > > -- Scott Nelson, WA6BLF > > > > On Aug 29, 2017, at 3:56 PM, Cory (NQ1E) <cory(a)nq1e.hm> wrote: > > > > Unfortunately, that's based on the list of name servers in the > > authoritative zone file and not based on the list of servers in effect as > > set by the dot org registry. > > > > I've expanded on Tom's script to take that into account and found there's > > apparently a couple of servers not answering at all. > > > > > > $ cat nssoa.sh > > #!/bin/bash > > ZONE=${1:-ampr.org} > > PARENTDOMAIN=$(echo -n $ZONE | cut -d'.' -f 2-) > > REGISTRYNS=$(dig -t ns +short $PARENTDOMAIN | tail -n1) > > for nameserver in $(dig +norecurse +authority +noadditional @$REGISTRYNS > > $ZONE | grep -i ^$ZONE | cut -f 6); do > > echo "$(dig +short soa @$nameserver $ZONE | cut -d' ' -f3)" > > "$nameserver" > > done > > > > $ ./nssoa.sh | sort > > dig: couldn't get address for 'ns.nonanet.net.uk.': not found > > 1708281715 ns1.defaultroute.net. > > 1708282030 munnari.oz.au. > > 1708291800 ampr-dns.in-berlin.de. > > 1708291800 ampr.org. > > 1708291800 ns2.threshinc.com. > > ns.nonanet.net.uk. > > timed hamradio.ucsd.edu. > > > > > > > > > > > > On Tue, Aug 29, 2017 at 11:55 AM, Brian Kantor <Brian(a)ucsd.edu> wrote: > > > >> Yes, that is very helpful. Thank you. > >> - Brian > >> > >> > >> On Tue, Aug 29, 2017 at 11:51:24AM -0700, Tom Hayward wrote: > >>> On Tue, Aug 29, 2017 at 11:11 AM, Brian Kantor <Brian(a)ucsd.edu> wrote: > >>>> The way to tell if a particular nameserver is current is to examine > >>>> the serial number in the ampr.org SOA record as retrieved from it > >>>> and compare that with the SOA from ampr.org (44.0.0.1). I use the > >>>> 'dig' tool for this purpose; there are other tools as well. > >>> > >>> Brian, > >>> > >>> Here is a script you might find useful for diagnostics. > >>> > >>> $ cat nssoa.sh > >>> #!/bin/bash > >>> ZONE=${1:-ampr.org} > >>> for nameserver in $(dig +short ns $ZONE); do > >>> echo "$(dig +short soa @$nameserver $ZONE | cut -d' ' -f3)" > >> "$nameserver" > >>> done > >>> > >>> $ ./nssoa.sh | sort > >>> 1708281715 ns0.comgw.net. > >>> 1708282030 munnari.OZ.AU. > >>> 1708282030 ns1.defaultroute.net. > >>> 1708291000 ampr-dns.in-berlin.de. > >>> 1708291800 ampr.org. > >>> 1708291800 ns2.threshinc.com. > >>> > >>> Tom KD7LXL > >>> _________________________________________ > >>> 44Net mailing list > >>> 44Net(a)hamradio.ucsd.edu > >>> http://hamradio.ucsd.edu/mailman/listinfo/44net > >> _________________________________________ > >> 44Net mailing list > >> 44Net(a)hamradio.ucsd.edu > >> http://hamradio.ucsd.edu/mailman/listinfo/44net > >> > >