From: "Rob Golding" <rob.golding@astutium•com>
To: <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] DNS seeds unstable
Date: Fri, 16 May 2014 18:17:17 +0100 [thread overview]
Message-ID: <009d01cf712a$b0577340$110659c0$@golding@astutium.com> (raw)
In-Reply-To: <ll5ems$6pt$1@ger.gmane.org>
> > 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
> > testnet-seed.bitcoin.petertodd.org SERVFAIL, just from Telefonica
Similarly no response from the alias'd aws dns service on 23.21.243.183
(testnet-seed-ns1.bitcoin.petertodd.org) from various test locations in
Europe
If there's a requirement for a domain & highly redundant dns to hard-code
into something, and one of the dev's drops me an email, I can get that
organised FoC, but these issues look like 'common'
firewall/transit/connectivity issues at first glance.
Rob
next prev parent reply other threads:[~2014-05-16 17:17 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 [this message]
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='009d01cf712a$b0577340$110659c0$@golding@astutium.com' \
--to=rob.golding@astutium$(echo .)com \
--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