{"type":"rich","version":"1.0","author_name":"npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","author_url":"https://nostr.ae/npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-05-25\n📝 Original message:Thanks for looking at the issue.\n\nUnfortunately, it still fails for me:\n\n$ nslookup testnet-seed.bitcoin.petertodd.org\nServer:\t\t127.0.1.1\nAddress:\t127.0.1.1#53\n\n** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL\n\nLike I said, can you look at the logfiles how the requests arrive?\n\nWhat particular thing did you fix? It would be good to know for future\noutages.\n\n\nOn 05/24/2014 12:17 AM, Peter Todd wrote:\n\u003e FWIW\n\u003e \n\u003e That said, keep in mind the github discussion(1) that was had: if all\n\u003e the DNS seeds being down breaks your application, your application is\n\u003e broken and insecure. The only exception is initial startup, and even\n\u003e then you should have fallbacks such as hardcoded node lists and manual\n\u003e peer entry. If for some reason you really do need instant startup, run\n\u003e your own centralized high-availability/low-latency nodes; either way\n\u003e you're depending on a centralized resource.\n\u003e \n\u003e 1) https://github.com/bitcoin/bitcoin/pull/4203"}