Raphael Wimmer<p>Having trouble connecting to <a href="https://hci.social/tags/pubmed" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pubmed</span></a> ?<br>It seems someone shut down the NIH DNS servers. People who still can connect to <a href="https://hci.social/tags/PubMed" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PubMed</span></a>, <a href="https://hci.social/tags/BLAST" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BLAST</span></a>, etc. are probably using DNS servers who cached their IP addresses.<br>(I can confirm that right now PubMed and BLAST are up, but not resolvable) </p><p><a href="https://www.nslookup.io/domains/pubmed.ncbi.nlm.nih.gov/dns-records/#authoritative" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">nslookup.io/domains/pubmed.ncb</span><span class="invisible">i.nlm.nih.gov/dns-records/#authoritative</span></a></p><p>Workaround: put this in your /etc/hosts :</p><p>34.107.134.59 pubmed.ncbi.nlm.nih.gov<br>130.14.250.10 ftp.wip.ncbi.nlm.nih.gov<br>130.14.250.10 ftp.ncbi.nlm.nih.gov<br>130.14.29.110 blast.ncbi.nlm.nih.gov</p>