Post AreVCWyw83G8Om1ctU by jspath55@chaos.social
 (DIR) More posts by jspath55@chaos.social
 (DIR) Post #AreSKnizSoCsmOonia by rysiek@mstdn.social
       2025-03-01T23:25:11Z
       
       0 likes, 1 repeats
       
       Edit: seems like they respond only on TCP?It seems like nih.gov nameservers are down – unless my euro-commie IP address is being blocked (which would be weird).Can someone from the US please check?ns.nih.gov.             3600    IN      A       128.231.128.251ns2.nih.gov.            3600    IN      A       128.231.64.1ns3.nih.gov.            3600    IN      A       165.112.4.230#SysAdmin #InfoSec
       
 (DIR) Post #AreSKoce7sj5Z0rFT6 by jspath55@chaos.social
       2025-03-01T23:27:10Z
       
       0 likes, 0 repeats
       
       @rysiek $ fping 128.231.128.251 128.231.64.1  165.112.4.230128.231.128.251 is unreachable128.231.64.1 is unreachable165.112.4.230 is unreachable
       
 (DIR) Post #AreSKpDVuoDVPM6gvw by bortzmeyer@mastodon.gougere.fr
       2025-03-02T17:49:56Z
       
       0 likes, 0 repeats
       
       @jspath55 @rysiek This is not a good test. ICMP echoes may be blocked but DNS still working. (The fact that they still reply over TCP indicate that it is not a network (layer 3) issue.
       
 (DIR) Post #AreSKvHdMP4sDs54Bk by rysiek@mstdn.social
       2025-03-01T23:26:42Z
       
       0 likes, 0 repeats
       
       $ kdig @ns.nih.gov. A nih.gov.;; WARNING: response timeout for 128.231.128.251@53(UDP)(…);; ERROR: failed to query server ns.nih.gov.@53(UDP)$ kdig @ns2.nih.gov. A nih.gov.;; WARNING: response timeout for 128.231.64.1@53(UDP)(…);; ERROR: failed to query server ns2.nih.gov.@53(UDP)$ kdig @ns3.nih.gov. A nih.gov.;; WARNING: response timeout for 165.112.4.230@53(UDP)(…);; ERROR: failed to query server ns3.nih.gov.@53(UDP)
       
 (DIR) Post #AreSKw5GNsmChnIhXs by jspath55@chaos.social
       2025-03-01T23:52:18Z
       
       0 likes, 0 repeats
       
       More fping results for the NIH name servers:$ date ; fping --name ns1.nih.gov ns2.nih.gov ns3.nih.gov ; dateSat Mar  1 23:50:49 UTC 2025ns1.nih.gov: Temporary failure in name resolutionns3.nih.gov: Temporary failure in name resolutionns2.nih.gov: error while sending ping: No route to hostns2.nih.gov is unreachableSat Mar  1 23:51:04 UTC 2025
       
 (DIR) Post #AreSL35WLK8qQcTVQ0 by rysiek@mstdn.social
       2025-03-01T23:28:29Z
       
       0 likes, 0 repeats
       
       Huh? They respond only on TCP?$ kdig +tcp +short @ns.nih.gov. A nih.gov.156.40.212.210$ kdig +tcp +short @ns2.nih.gov. A nih.gov.156.40.212.210$ kdig +tcp +short @ns3.nih.gov. A nih.gov.156.40.212.210
       
 (DIR) Post #AreVCWyw83G8Om1ctU by jspath55@chaos.social
       2025-03-02T18:22:07Z
       
       0 likes, 0 repeats
       
       @bortzmeyer OK.lynx: Can't access startfile https://www.nih.gov/