{"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-16\n📝 Original message:On 05/15/2014 07:48 PM, Gregory Maxwell wrote:\n\u003e On Thu, May 15, 2014 at 4:50 AM, Andreas Schildbach\n\u003e \u003candreas at schildbach.de\u003e wrote:\n\u003e\u003e I'm bringing this issue up again. The current Bitcoin DNS seed\n\u003e\u003e infrastructure is unstable. I assume this is because of we're using a\n\u003e\u003e custom DNS implementation which is not 100% compatible. There have been\n\u003e\u003e bugs in the past, like a case sensitive match for the domain name.\n\u003e\n\u003e If software is using the DNS seeds in a way where one or two being\n\u003e unavailable is problematic, then the software may be using them\n\u003e poorly.\n\u003e\n\u003e Generally DNS seeds should only be used as fast connectivity hints,\n\u003e primarily for initial connectivity. Relying on them exclusively\n\u003e increases isolation vulnerabilities (e.g. because the dns seed\n\u003e operators or any ISP or network attacker on the path between you and\n\u003e the seeds can replace the results with ones that isolate you on a\n\u003e bogus network).\n\nI just used \"nslookup\", after seeing the issues in bitcoinj.\n\nI agree that clients should be robust regarding DNS lookups (and\nbitcoinj isn't), but still I think the first step needs to be\nmaintaining a quality infrastructure."}