public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Alex Kotenko <alexykot@gmail.com>
To: Andreas Schildbach <andreas@schildbach.de>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Date: Wed, 21 May 2014 12:10:52 +0100	[thread overview]
Message-ID: <CALDj+BZ-F31aWURYX_SF+aYxfz2KxeynspLACzBxbmXnCUx4xw@mail.gmail.com> (raw)
In-Reply-To: <lli161$81k$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 5260 bytes --]

Misunderstanding. Both seeds are available on port 53 via BIND forwarding.
Just also each DNS seed is available separately on it's own port.


Best regards,
Alex Kotenko


2014-05-21 12:03 GMT+01:00 Andreas Schildbach <andreas@schildbach.de>:

> Great, thanks for this contribution!
>
> Do you plan to have your seeds reachable on port 53 eventually?
> Currently bitcoinj cannot deal with nonstandard ports I think.
>
>
> On 05/21/2014 11:23 AM, Alex Kotenko wrote:
> > 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 <http://node.alexykot.me> bitcoin-seed.alexykot.me
> > <http://bitcoin-seed.alexykot.me> A
> > or directly
> > dig -p 8353 @node.alexykot.me <http://node.alexykot.me>
> > bitcoin-seed.alexykot.me <http://bitcoin-seed.alexykot.me> A
> >
> > testnet seed
> > dig @node.alexykot.me <http://node.alexykot.me> testnet-seed.alexykot.me
> > <http://testnet-seed.alexykot.me> A
> > or directly
> > dig -p 18353 @node.alexykot.me <http://node.alexykot.me>
> > testnet-seed.alexykot.me <http://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 <robert@mckay.com
> > <mailto:robert@mckay.com>>:
> >
> >     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 <robert@mckay.com
> >     <mailto:robert@mckay.com>>
> >     >> 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
> >     <mailto:Bitcoin-development@lists.sourceforge.net>
> >     https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > "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
> >
>
>
>
>
> ------------------------------------------------------------------------------
> "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
>

[-- Attachment #2: Type: text/html, Size: 9257 bytes --]

  reply	other threads:[~2014-05-21 11:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 11:50 [Bitcoin-development] DNS seeds unstable Andreas Schildbach
2014-05-15 17:17 ` Drak
2014-05-15 17:41 ` Jeff Garzik
2014-05-15 17:48 ` Gregory Maxwell
2014-05-16  9:15   ` Andreas Schildbach
2014-05-16 14:09     ` Mike Hearn
2014-05-15 18:05 ` Luke Dashjr
2014-05-16 16:34 ` Andreas Schildbach
2014-05-16 16:46   ` Matt Whitlock
2014-05-16 16:46   ` Laszlo Hanyecz
2014-05-16 17:07     ` Alex Kotenko
2014-05-16 22:02       ` Jeff Garzik
2014-05-17  0:58         ` Alex Kotenko
2014-05-17 11:39           ` Andreas Schildbach
2014-05-17 12:02             ` Alex Kotenko
2014-05-17 12:39               ` Andreas Schildbach
2014-05-19 20:14                 ` Alex Kotenko
2014-05-19 20:22                   ` Michael Wozniak
2014-05-19 20:38                     ` Alex Kotenko
2014-05-19 20:36                   ` Robert McKay
2014-05-19 23:49                     ` Jeff Garzik
2014-05-20  0:44                       ` Robert McKay
2014-05-20  0:50                         ` Robert McKay
2014-05-21  9:23                           ` Alex Kotenko
2014-05-21 11:03                             ` Andreas Schildbach
2014-05-21 11:10                               ` Alex Kotenko [this message]
2014-05-21 11:26                                 ` Andreas Schildbach
     [not found]                                   ` <537DBC3C.4090907@schildbach.de>
2014-06-11 13:57                                     ` Alex Kotenko
2014-06-11 14:24                                       ` Andreas Schildbach
2014-05-20  0:45                       ` Michael Wozniak
2014-05-16 17:17   ` Rob Golding
2014-05-16 17:34     ` Nick Simpson
2014-05-16 21:46     ` Luke Dashjr
2014-05-16 18:53 ` Matt Corallo
2014-05-16 19:43   ` Andreas Schildbach
     [not found]   ` <8ADB6ABE-371C-4F4A-A003-F6751B01A12F@heliacal.net>
     [not found]     ` <53766148.1000708@bluematt.me>
2014-05-17  1:06       ` Matt Corallo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALDj+BZ-F31aWURYX_SF+aYxfz2KxeynspLACzBxbmXnCUx4xw@mail.gmail.com \
    --to=alexykot@gmail.com \
    --cc=andreas@schildbach.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox