From: Drak <drak@zikula•org>
To: Andreas Schildbach <andreas@schildbach•de>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Date: Thu, 15 May 2014 18:17:29 +0100 [thread overview]
Message-ID: <CANAnSg24Hhvb0T5Cu5yw=hbeF95mbDeVqLfY-5idH7zT95Sp0g@mail.gmail.com> (raw)
In-Reply-To: <ll29m5$r6c$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]
I am sure the failure here is probably more mundane like a a service not
restarted, or not on auto restart when server is rebooted and such like.
The dns seeder works pretty efficiently in my experience. Maybe we need
more seeders and to include the ability for zone transfers so existing
seeders can spread their records to multiple servers running standard DNS
servers like bind etc.
On 15 May 2014 12:50, Andreas Schildbach <andreas@schildbach•de> wrote:
> I'm bringing this issue up again. The current Bitcoin DNS seed
> infrastructure is unstable. I assume this is because of we're using a
> custom DNS implementation which is not 100% compatible. There have been
> bugs in the past, like a case sensitive match for the domain name.
>
> Current state (seeds taken from bitcoinj):
>
> mainnet:
>
> seed.bitcoin.sipa.be OK
> dnsseed.bluematt.me OK
> dnsseed.bitcoin.dashjr.org SERVFAIL, tried multiple ISPs
> seed.bitcoinstats.com OK
>
> testnet:
>
> testnet-seed.bitcoin.petertodd.org SERVFAIL, just from Telefonica
> testnet-seed.bluematt.me OK (but only returns one node)
>
> Note: Telefonica is one of Europe's largest ISPs.
>
> I would try to improve DNS myself, but I'm not capable of writing C. My
> "fix" would be to reimplement everything in Java -- I doubt you guys
> would be happy with that.
>
>
>
> ------------------------------------------------------------------------------
> "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: 3095 bytes --]
next prev parent reply other threads:[~2014-05-15 17:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 11:50 Andreas Schildbach
2014-05-15 17:17 ` Drak [this message]
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
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='CANAnSg24Hhvb0T5Cu5yw=hbeF95mbDeVqLfY-5idH7zT95Sp0g@mail.gmail.com' \
--to=drak@zikula$(echo .)org \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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