From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wn2ke-0000SB-8R for bitcoin-development@lists.sourceforge.net; Wed, 21 May 2014 09:23:56 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.181 as permitted sender) client-ip=209.85.220.181; envelope-from=alexy.kot.all@gmail.com; helo=mail-vc0-f181.google.com; Received: from mail-vc0-f181.google.com ([209.85.220.181]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wn2kc-0001tb-5E for bitcoin-development@lists.sourceforge.net; Wed, 21 May 2014 09:23:56 +0000 Received: by mail-vc0-f181.google.com with SMTP id ld13so2122458vcb.40 for ; Wed, 21 May 2014 02:23:48 -0700 (PDT) X-Received: by 10.58.195.202 with SMTP id ig10mr7107846vec.33.1400664228593; Wed, 21 May 2014 02:23:48 -0700 (PDT) MIME-Version: 1.0 Sender: alexy.kot.all@gmail.com Received: by 10.58.211.135 with HTTP; Wed, 21 May 2014 02:23:08 -0700 (PDT) In-Reply-To: References: <09E70F88-DA1C-4E3F-9342-547FB8794EAB@heliacal.net> <779f3ed92d29cfd6922a92c5d60d3f9d@webmail.mckay.com> <0f40d061612966ff809fff04d3f698eb@webmail.mckay.com> From: Alex Kotenko Date: Wed, 21 May 2014 10:23:08 +0100 X-Google-Sender-Auth: O1biOgyiSjvE7fzt8c8gKxW4_5Q Message-ID: Cc: Bitcoin Dev Content-Type: multipart/alternative; boundary=047d7b66fce7cb880104f9e58d74 X-Spam-Score: 0.9 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (alexy.kot.all[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header 1.0 HTML_MESSAGE BODY: HTML included in message 0.3 HTML_FONT_FACE_BAD BODY: HTML font face is not a word -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wn2kc-0001tb-5E Subject: Re: [Bitcoin-development] DNS seeds unstable X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 09:23:56 -0000 --047d7b66fce7cb880104f9e58d74 Content-Type: text/plain; charset=UTF-8 okay, I've set it up with bind forwarding requests to two dnsseeds running on separate ports. Though I see a problem with testnet DNS seed itself. It runs, but somehow it only returns one IP address. Exactly same DNS seeder looking for mainnet nodes is working fine. You can reach seeds through mainnet seed: dig @node.alexykot.me bitcoin-seed.alexykot.me A or directly dig -p 8353 @node.alexykot.me bitcoin-seed.alexykot.me A testnet seed dig @node.alexykot.me testnet-seed.alexykot.me A or directly dig -p 18353 @node.alexykot.me testnet-seed.alexykot.me A So what can be the problem with testnet DNS seeder? Best regards, Alex Kotenko 2014-05-20 1:50 GMT+01:00 Robert McKay : > On Tue, 20 May 2014 01:44:29 +0100, Robert McKay wrote: > > On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote: > >> On Mon, May 19, 2014 at 4:36 PM, Robert McKay > >> wrote: > >>> It should be possible to configure bind as a DNS forwarder.. this > >>> can > >>> be done in a zone context.. then you can forward the different > >>> zones > >>> to > >>> different dnsseed daemons running on different non-public IPs or > >>> two > >>> different ports on the same IP (or on one single non-public IP > >>> since > >>> there's really no reason to expose the dnsseed directly daemon at > >>> all). > >> > >> Quite the opposite. dnsseed data rotates through a lot of addresses > >> if available. Using the bind/zone-xfer system would result in fewer > >> total addresses going through to the clients, thanks to the addition > >> of caching levels that the bind/zone-xfer system brings. > >> > >> That said, if the choice is between no-service and bind, bind it is > >> ;p > > > > Setting it up as a zone forwarder causes each request to go through > > to > > the dnsseed backend for each request. > > This stackoverflow describes a similar situation; > > http://stackoverflow.com/questions/15338232/how-to-forward-a-subzone > > you can additionally specify the port to forward too; > > http://www.zytrax.com/books/dns/ch7/queries.html#forwarders > > it should be possible to forward to different ports on 127.0.0.1 for > each dnsseed instance. > > Rob > > > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. > Get unparalleled scalability from the best Selenium testing platform > available > Simple to use. Nothing to install. Get started now for free." > http://p.sf.net/sfu/SauceLabs > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --047d7b66fce7cb880104f9e58d74 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
okay, I've set it up with bi= nd forwarding requests to two dnsseeds running on separate ports. Though I = see a problem with testnet DNS seed itself. It runs, but somehow it only re= turns one IP address. Exactly same DNS seeder looking for mainnet nodes is = working fine.=C2=A0

You can reach= seeds through
mainnet seed:
dig @node.alexykot.me bitcoin-seed.alexykot.me A
or directly
dig -p 8353 @= node.alexykot.me bitcoin-seed.alexykot.me A

testnet seed<= /font>
dig @node.alexykot.me testnet-seed.alexykot.me= A
or directly
=

So what can be the problem with testnet DNS seeder?


Best regards,=C2=A0
Alex Kotenko


2014-05-20 1:50 GMT+01:00 Robert McKay <= span dir=3D"ltr"><= robert@mckay.com>:
On Tue, 20 May 2014 01:44:29 +0100, Rober= t McKay wrote:
> On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:
>> On Mon, May 19, 2014 at 4:36 PM, Robert McKay <robert@mckay.com>
>> wrote:
>>> It should be possible to configure bind as a DNS forwarder.. t= his
>>> can
>>> be done in a zone context.. then you can forward the different=
>>> zones
>>> to
>>> different dnsseed daemons running on different non-public IPs = or
>>> two
>>> different ports on the same IP (or on one single non-public IP=
>>> since
>>> there's really no reason to expose the dnsseed directly da= emon at
>>> all).
>>
>> Quite the opposite. =C2=A0dnsseed data rotates through a lot of ad= dresses
>> if available. =C2=A0Using the bind/zone-xfer system would result i= n fewer
>> total addresses going through to the clients, thanks to the additi= on
>> of caching levels that the bind/zone-xfer system brings.
>>
>> That said, if the choice is between no-service and bind, bind it i= s
>> ;p
>
> Setting it up as a zone forwarder causes each request to go through > to
> the dnsseed backend for each request.

This stackoverflow describes a similar situation;

http://stackoverflow.com/questions/15338232/how-to-= forward-a-subzone

you can additionally specify the port to forward too;

http://www.zytrax.com/books/dns/ch7/queries.html#forwarders<= /a>

it should be possible to forward to different ports on 127.0.0.1 for
each dnsseed instance.

Rob

---------------------------------------------------------------------------= ---
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE=
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform availa= ble
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net= /sfu/SauceLabs
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitc= oin-development

--047d7b66fce7cb880104f9e58d74--