DNSSEC and time.nist.gov
daved at nostrum.com
Fri Aug 26 12:51:43 UTC 2016
I have not been successful in contacting the parties responsible for domains under .gov. Maybe hitting up their registrar will work for you.
In my experience, it will be fixed within a week's time. We see DNSSEC issues with different .gov domains two to three times a year.
> On Aug 26, 2016, at 3:37 AM, Stephane Bortzmeyer via Unbound-users <unbound-users at unbound.net> wrote:
> On Fri, Aug 26, 2016 at 10:12:03AM +0200,
> Rok Potočnik via Unbound-users <unbound-users at unbound.net> wrote
> a message of 9 lines which said:
>> If anyone of you guys has a direct contact would you be so kind and
>> notify them...
> Well, this is quite simple, use whois :
> % whois nist.gov
> % DOTGOV WHOIS Server ready
> Domain Name: NIST.GOV
> Status: ACTIVE
>>>> Last update of whois database: 2016-08-26T08:37:05Z <<<
> Please be advised that this whois server only contains information pertaining
> to the .GOV domain. For information for other domains please use the whois
> server at RS.INTERNIC.NET.
> OK, I mean, use the DNS:
> % dig +short SOA nist.gov
> gm.nist.gov. please_set_email.absolutely.nowhere. 1221679 10800 1080 2419200 300
> SOA 7 2 1800 20160902083535 20160826073535 1214 nist.gov. T4NfR25TRRdevhKoPPuk9mAse7q8+sxvKQgmh8KsVu3FYdIsqIgApjiG 1JJu/Jqf1vIJV2mcne/g0VUPUmGY0Cw8p8yhWbntIsW/Wo+TIU4iuUJN D6H7mxpejKS2l0M6omJnIZ8OXI5PsmNhwT+A2Mw2LprJXkiUe4nho04A kBU=
> SOA 7 2 1800 20160902083535 20160826073535 9830 nist.gov. mJRYF2avTTuzvkDzbiVpurN/TksEie1Q5FmgE4DpWXJGv8d8TB0r3S1t S8EXYsBzIvysZlLnj0VDO62LY+OiLBmk/TzwnCSv89PrGRGngBG6LpuE 3Hl5xekkbxCVA40Fm1S0x9l0VMOmakXlfuz4U/t4UX9/yrLtlLjXpnCl +lM=
> OK, I give in :-)
More information about the Unbound-users