rich1.0npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7njumphttps://nostr.ae📅 Original date posted:2014-05-25 📝 Original message:Thanks for looking at the issue. Unfortunately, it still fails for me: $ nslookup testnet-seed.bitcoin.petertodd.org Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL Like I said, can you look at the logfiles how the requests arrive? What particular thing did you fix? It would be good to know for future outages. On 05/24/2014 12:17 AM, Peter Todd wrote: > FWIW > > That said, keep in mind the github discussion(1) that was had: if all > the DNS seeds being down breaks your application, your application is > broken and insecure. The only exception is initial startup, and even > then you should have fallbacks such as hardcoded node lists and manual > peer entry. If for some reason you really do need instant startup, run > your own centralized high-availability/low-latency nodes; either way > you're depending on a centralized resource. > > 1) https://github.com/bitcoin/bitcoin/pull/4203