public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Testnet DNS seed
Date: Thu, 24 Jan 2013 02:01:03 -0500	[thread overview]
Message-ID: <20130124070103.GA30820@savin> (raw)

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

I setup a testnet DNS seed using Pieter Wuille's bitcoin-seeder, with
some simple modifications for testnet. It's at
testnet-seed.bitcoin.petertodd.org I also created
static-testnet-seed.bitcoin.petertodd.org which currently has a single A
record pointing to a testnet node I'm running to bootstrap the seeder
itself.

Everything is running on a dedicated Amazon EC2 micro instance. Just
IPv4 is supported right now as EC2 doesn't support IPv6; even tunnels
are broken. I also haven't setup tor yet. I can do both if there is
demand.

I guess the next step is to create a new strTestNetDNSSeed in the
satoshi client, although it'd be better if at least one more person had
a testnet seed to include in the list. Probably best to leave IRC
enabled too.

Also, FWIW, it looks like the pnSeed list is way out of date...

Pieter: Have you written any start/stop/monitoring scripts for the
seeder? My mods are at git://github.com/petertodd/bitcoin-seeder.git in
the "testnet" branch. I'll send you a pull request once it's had some
testing.

-- 
'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2013-01-24  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  7:01 Peter Todd [this message]
2013-01-26  2:23 ` [Bitcoin-development] Testnet DNS seed Jeff Garzik
2013-01-27 10:27   ` Peter Todd
2013-01-27 16:14     ` Jeff Garzik
2013-01-27 16:18     ` Pieter Wuille

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=20130124070103.GA30820@savin \
    --to=pete@petertodd.org \
    --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