public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] DNS seeds unstable
Date: Fri, 16 May 2014 21:46:00 +0000	[thread overview]
Message-ID: <201405162146.01429.luke@dashjr.org> (raw)
In-Reply-To: <009d01cf712a$b0577340$110659c0$@golding@astutium.com>

On Friday, May 16, 2014 5:17:17 PM Rob Golding wrote:
> > > dnsseed.bitcoin.dashjr.org		SERVFAIL, tried multiple ISPs
> 
> dnsseed.bitcoin.dashjr.org. 60  IN      NS      jun.dashjr.org.
> but jun.dashjr.org isn't responding to dns queries (as at 18.10 GMT
> 2014-05-16)
> 
> that would be a fundamental problem with the dns infrastructure for that
> domain (and the sub-hosts/records) , with the authoritive server not
> replying to the dns query

jun.dashjr.org has resolved 130 requests in the past ~12 hours, and I can see 
it resolving more in tcpdump. I do observe two potential problems, however:

- For the past 24-48 hours, there seem to be some significant routing problems 
on the IPv4 internet, resulting in people using various diverse ISPs 
(including myself at home) being unable to route to any of my servers. This 
issue doesn't affect IPv6, however.

- The DNS seeder seems to only be responding to requests received over IPv4. 
This means IPv6 DNS servers get no response. :(

Luke



  parent reply	other threads:[~2014-05-16 21:46 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
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 [this message]
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=201405162146.01429.luke@dashjr.org \
    --to=luke@dashjr$(echo .)org \
    --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