<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2011-08-03&#xA;🗒️ Summary of this message: Many bad nodes are appearing in the DNS seeds, slowing down peer bringup for Android apps. A custom DNS server may help resolve the issue.&#xA;📝 Original message:This is expected to happen from time to time of course as it&#39;s inherently&#xA;racy, but there are a *lot* of bad nodes appearing in the DNS seeds.&#xA;&#xA;$ nmap -oG /tmp/x -p 8333 `dig +short bitseed.bitcoin.org.uk&#xA;dnsseed.bluematt.me bitseed.xf2.org`&#xA;...&#xA;Nmap done: 48 IP addresses (25 hosts up) scanned in 9.80 seconds&#xA;&#xA;$ grep -c &#39;closed&#39; /tmp/x&#xA;6&#xA;&#xA;So of 48 IPs returned only 19 are actually usable. This is slowing down peer&#xA;bringup for the Android apps, which don&#39;t currently save the addresses of&#xA;last-used peers (yes, I know we should fix this).&#xA;&#xA;I was talking to a friend a few days ago about Bitcoin, he seemed&#xA;interested. I&#39;m hoping he might take on DNS seeding as a project. A custom&#xA;DNS server that watches the network to find long-lived peers that run the&#xA;latest version would be helpful for resolving this kind of thing.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110803/2d5c0a64/attachment.html&gt;</html></oembed>