public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Date: Fri, 16 May 2014 16:09:28 +0200	[thread overview]
Message-ID: <CANEZrP0Eocd7CFXoW=meatRtcf-wVRQ=uE70exwO-aQJiYss_Q@mail.gmail.com> (raw)
In-Reply-To: <ll4kvl$3nu$1@ger.gmane.org>

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

My android wallet is working OK. Yes it isn't great when seeds have
temporary availability problems but things are still working.

There's a couple of pull reqs outstanding to include hard coded seed peers
and getaddr sourced IPs. Once those are finished and merged in there'll be
more backup paths.
On 16 May 2014 11:16, "Andreas Schildbach" <andreas@schildbach.de> wrote:

> On 05/15/2014 07:48 PM, Gregory Maxwell wrote:
> > On Thu, May 15, 2014 at 4:50 AM, 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.
> >
> > If software is using the DNS seeds in a way where one or two being
> > unavailable is problematic, then the software may be using them
> > poorly.
> >
> > Generally DNS seeds should only be used as fast connectivity hints,
> > primarily for initial connectivity. Relying on them exclusively
> > increases isolation vulnerabilities (e.g. because the dns seed
> > operators or any ISP or network attacker on the path between you and
> > the seeds can replace the results with ones that isolate you on a
> > bogus network).
>
> I just used "nslookup", after seeing the issues in bitcoinj.
>
> I agree that clients should be robust regarding DNS lookups (and
> bitcoinj isn't), but still I think the first step needs to be
> maintaining a quality infrastructure.
>
>
>
>
> ------------------------------------------------------------------------------
> "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: 2930 bytes --]

  reply	other threads:[~2014-05-16 14:09 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 [this message]
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='CANEZrP0Eocd7CFXoW=meatRtcf-wVRQ=uE70exwO-aQJiYss_Q@mail.gmail.com' \
    --to=mike@plan99.net \
    --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