{"type":"rich","version":"1.0","author_name":"npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","author_url":"https://nostr.ae/npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-05-26\n📝 Original message:On Sun, May 25, 2014 at 09:12:10PM +0200, Andreas Schildbach wrote:\n\u003e Thanks for looking at the issue.\n\u003e \n\u003e Unfortunately, it still fails for me:\n\u003e \n\u003e $ nslookup testnet-seed.bitcoin.petertodd.org\n\u003e Server:\t\t127.0.1.1\n\u003e Address:\t127.0.1.1#53\n\u003e \n\u003e ** server can't find testnet-seed.bitcoin.petertodd.org: SERVFAIL\n\u003e \n\u003e Like I said, can you look at the logfiles how the requests arrive?\n\nThere are no logfiles for DNS requests.\n\nI just checked on EC2 and my cellphone internet connection here in Tel\nAviv; both work fine. My best guess is that your DNS resolver locally or\nat your ISP is unable to deal with the fact that the second DNS seed\nserving the domain testnet-seed.bitcoin.petertodd.org happens to be down\nright now. Note that some ISP's appear to both run buggy DNS servers,\nand redirect traffic meant to go to Google's 8.8.8 and 8.8.4.4 DNS\nservers to their own servers.\n\nI'd suggest that someone setup an alternate HTTP(S) based DNS seed for\nprotocol redundency.\n\n\u003e What particular thing did you fix? It would be good to know for future\n\u003e outages.\n\nDunno exactly. It appeared to be running fine when I logged into the\nmachine, but for whatever reason DNS requests just weren't getting\nresolved. Restarted and it was ok again.\n\n-- \n'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 490 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140526/c87df7ed/attachment.sig\u003e"}