nih.gov NS only answers TCP queries

[Jan Schaumann]

Hey,

This was reported on Mastodon[1][2]:

It looks like currently the NS for nih.gov only
respond to TCP queries.

$ dig +noall +auth +add @a.ns.gov ns nih.gov
nih.gov.                10800   IN      NS ns.nih.gov.
nih.gov.                10800   IN      NS ns2.nih.gov.
nih.gov.                10800   IN      NS ns3.nih.gov.
ns.nih.gov.             3600    IN      A 128.231.128.251
ns2.nih.gov.            3600    IN      A 128.231.64.1
ns3.nih.gov.            3600    IN      A 165.112.4.230
$ dig +short +noall @165.112.4.230 ns nih.gov
;; connection timed out; no servers could be reached
$ dig +short @128.231.64.1 ns nih.gov        
;; connection timed out; no servers could be reached
$ dig +short @128.231.128.251 ns nih.gov
;; connection timed out; no servers could be reached
$ dig +short +tcp @165.112.4.230 ns nih.gov  
ns.nih.gov.
ns3.nih.gov.
ns2.nih.gov.
$ dig +short +tcp @128.231.64.1  ns nih.gov
ns.nih.gov.
ns2.nih.gov.
ns3.nih.gov.
$ dig +short +tcp @128.231.128.251 ns nih.gov
ns3.nih.gov.
ns.nih.gov.
ns2.nih.gov.
$ 

Wonder if that's some DOGE fallout.  I've reached out
to hostmaster at list.nih.gov (by resolving the IP
address via TCP and adding it to /etc/hosts :-), but I
wouldn't assume that this actually gets to somebody
able to fix things.

-Jan

[1] https://mstdn.social/@rysiek/114089755401568345
[2] https://cyberplace.social/@GossiTheDog/114089601659176174