From: Michael Wozniak <mw@osfda.org>
To: Alex Kotenko <alexykot@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Date: Mon, 19 May 2014 16:22:46 -0400 [thread overview]
Message-ID: <8E95FB7C-CFC5-410D-B8AF-8F227BA852F6@osfda.org> (raw)
In-Reply-To: <CALDj+BamyawuTgDhzM0AyB5LWNPb_xY_BQeDHqs9t9WLPibiCQ@mail.gmail.com>
I’m not familiar with how the daemon works, however could you set up two daemons listening local on different ports and with a separate daemon or normal dns server that proxies incoming queries to either domain? I don’t know if standard DNS servers would support that, or if you would need a custom proxy application.
-
Michael Wozniak
On May 19, 2014, at 4:14 PM, Alex Kotenko <alexykot@gmail.com> wrote:
> Hmm, I've mostly setup what's promised, testing DNS seeds now. There is one problem I see that I can't really solve myself.
> This dnsseed daemon cannot serve more than one name at once, which means that I cannot serve testnet and mainnet seeds off one daemon instance which means I need to buy two IP addresses for it. That's unfortunate as it needs much more spendings from me to operate, second IP address will cost nearly as much as the server itself.
>
> Can anybody help with this? I cannot into C++ to fix that myself.
>
>
> Best regards,
> Alex Kotenko
>
>
> 2014-05-17 13:39 GMT+01:00 Andreas Schildbach <andreas@schildbach.de>:
> On 05/17/2014 02:02 PM, Alex Kotenko wrote:
>
> > So, my understanding is that atm we have no working DNS seeds at the
> > testnet3, right? There are two DNS seeds known, of which one is
> > unreachable atm, and another one is giving just one IP address, which is
> > also a dead node.
>
> Yes, that's my understanding too.
>
> > If I'll start a DNS seed of my own and make sure it works well, will
> > this help?
>
> Yes, definately.
>
> > I've found this DNS seeder daemon
> > <https://github.com/sipa/bitcoin-seeder>, and it seems to be exactly
> > what I need to run a DNS seeder myself.
>
> Afaik this is what most of the other seeds are using, yes.
>
> > So if my understanding is correct, I'll setup a DNS seeds for mainnet
> > and for testnet at bitcoin-seed.alexykot.me
> > <http://bitcoin-seed.alexykot.me> and testnet-seed.alexykot.me
> > <http://testnet-seed.alexykot.me>, and also a well connected nodes for
> > mainnet and testnet on the same server.
> > Is this a good plan? Will this all help?
>
> Sound great! Let me know if you've got something to test.
>
>
>
> ------------------------------------------------------------------------------
> "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
next prev parent reply other threads:[~2014-05-19 20:39 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 [this message]
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
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=8E95FB7C-CFC5-410D-B8AF-8F227BA852F6@osfda.org \
--to=mw@osfda.org \
--cc=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