{"type":"rich","version":"1.0","author_name":"npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4","author_url":"https://nostr.ae/npub14jv7tj33yt72yk8mljmvkck3p4xm5s3mxfpj289up38qqsn9dhkqeh00t4","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-05-21\n📝 Original message:okay, I've set it up with bind forwarding requests to two dnsseeds running\non separate ports. Though I see a problem with testnet DNS seed itself. It\nruns, but somehow it only returns one IP address. Exactly same DNS seeder\nlooking for mainnet nodes is working fine.\n\nYou can reach seeds through\nmainnet seed:\ndig @node.alexykot.me bitcoin-seed.alexykot.me A\nor directly\ndig -p 8353 @node.alexykot.me bitcoin-seed.alexykot.me A\n\ntestnet seed\ndig @node.alexykot.me testnet-seed.alexykot.me A\nor directly\ndig -p 18353 @node.alexykot.me testnet-seed.alexykot.me A\n\nSo what can be the problem with testnet DNS seeder?\n\n\nBest regards,\nAlex Kotenko\n\n\n2014-05-20 1:50 GMT+01:00 Robert McKay \u003crobert at mckay.com\u003e:\n\n\u003e On Tue, 20 May 2014 01:44:29 +0100, Robert McKay wrote:\n\u003e \u003e On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:\n\u003e \u003e\u003e On Mon, May 19, 2014 at 4:36 PM, Robert McKay \u003crobert at mckay.com\u003e\n\u003e \u003e\u003e wrote:\n\u003e \u003e\u003e\u003e It should be possible to configure bind as a DNS forwarder.. this\n\u003e \u003e\u003e\u003e can\n\u003e \u003e\u003e\u003e be done in a zone context.. then you can forward the different\n\u003e \u003e\u003e\u003e zones\n\u003e \u003e\u003e\u003e to\n\u003e \u003e\u003e\u003e different dnsseed daemons running on different non-public IPs or\n\u003e \u003e\u003e\u003e two\n\u003e \u003e\u003e\u003e different ports on the same IP (or on one single non-public IP\n\u003e \u003e\u003e\u003e since\n\u003e \u003e\u003e\u003e there's really no reason to expose the dnsseed directly daemon at\n\u003e \u003e\u003e\u003e all).\n\u003e \u003e\u003e\n\u003e \u003e\u003e Quite the opposite.  dnsseed data rotates through a lot of addresses\n\u003e \u003e\u003e if available.  Using the bind/zone-xfer system would result in fewer\n\u003e \u003e\u003e total addresses going through to the clients, thanks to the addition\n\u003e \u003e\u003e of caching levels that the bind/zone-xfer system brings.\n\u003e \u003e\u003e\n\u003e \u003e\u003e That said, if the choice is between no-service and bind, bind it is\n\u003e \u003e\u003e ;p\n\u003e \u003e\n\u003e \u003e Setting it up as a zone forwarder causes each request to go through\n\u003e \u003e to\n\u003e \u003e the dnsseed backend for each request.\n\u003e\n\u003e This stackoverflow describes a similar situation;\n\u003e\n\u003e http://stackoverflow.com/questions/15338232/how-to-forward-a-subzone\n\u003e\n\u003e you can additionally specify the port to forward too;\n\u003e\n\u003e http://www.zytrax.com/books/dns/ch7/queries.html#forwarders\n\u003e\n\u003e it should be possible to forward to different ports on 127.0.0.1 for\n\u003e each dnsseed instance.\n\u003e\n\u003e Rob\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e \"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE\n\u003e Instantly run your Selenium tests across 300+ browser/OS combos.\n\u003e Get unparalleled scalability from the best Selenium testing platform\n\u003e available\n\u003e Simple to use. Nothing to install. Get started now for free.\"\n\u003e http://p.sf.net/sfu/SauceLabs\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140521/e7433ef3/attachment.html\u003e"}