This is expected to happen from time to time of course as it&#39;s inherently racy, but there are a <i>lot</i> of bad nodes appearing in the DNS seeds.<div><br></div><div><div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">$ nmap -oG /tmp/x -p 8333 `dig +short <a href="http://bitseed.bitcoin.org.uk">bitseed.bitcoin.org.uk</a> <a href="http://dnsseed.bluematt.me">dnsseed.bluematt.me</a> <a href="http://bitseed.xf2.org">bitseed.xf2.org</a>`</font></div>
</div></div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">...</font></div><div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">Nmap done: 48 IP addresses (25 hosts up) scanned in 9.80 seconds</font></div>
</div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace"><br></font></div><div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">$ grep -c &#39;closed&#39; /tmp/x</font></div>
<div><font class="Apple-style-span" face="&#39;courier new&#39;, monospace">6<br></font><br></div><div>So of 48 IPs returned only 19 are actually usable. This is slowing down peer bringup for the Android apps, which don&#39;t currently save the addresses of last-used peers (yes, I know we should fix this).</div>
<div><br></div><div>I was talking to a friend a few days ago about Bitcoin, he seemed interested. I&#39;m hoping he might take on DNS seeding as a project. A custom DNS server that watches the network to find long-lived peers that run the latest version would be helpful for resolving this kind of thing.</div>