📅 Original date posted:2011-06-13
🗒️ Summary of this message: DNS bootstrapping can be made more robust by hosting seeds on services like Zerigo and small VPS, and using namecoin's TLDs to avoid centralization. A simple DNS server build and script can be published for anyone to host, and seeds can be hardcoded or conventionally pointed to bitcoin.* domains. However, there may be concerns about potential attacks from poisoned seeds.
📝 Original message:Jeff is absolutely correct, stating that DNS bootstrapping can
potentially be very robust.
Consider, for example, that seeds can be hosted by services like
zerigo, who provide decent management API's, as well as by thousands
of small VPS operated by people all over the world. Moreover, if
namecoin lives up to it's promises than some seeds can be hosted using
it's tlds, and as such we would get around centralised ICANN/registrar
weakness.
The most practical way I see how to improve DNS bootstrapping is
publishing build instructions for a simple DNS server build and a
script which feeds it with node data. Something simple like djbdns plus
a perl script, or similar zerigo API script, would do. Than anyone can
host it. All left to do than is to hardcode a bunch of such DNS seeds
into the client.
Hardcoding seeds is not good enough? Get a convention that anyone
owning a bitcoin.* domain should point seed.bitcoin.* to a decent DNS
seed. Than clients simply scan 100-200 tld's to find working
seed.bitcoin.*
I am not quite sure, though, is if this would enable some attacks by
poisoned seeds.
Vladimir.
Vladimir Marchenko [ARCHIVE] /
npub1ya…f362l
2023-06-07 01:36:33
in reply to nevent1q…6xr4
Author Public Key
npub1yad6fmp7zh9rc0lpzecu5dtgy2yye4f7mvf3wdn8rulxntcx0czswf362lPublished at
2023-06-07 01:36:33Event JSON
{
"id": "f423dea06f8a9a29bfdaaebbb2ce6a84a22072b40932ce248ee8962561686973",
"pubkey": "275ba4ec3e15ca3c3fe11671ca356822884cd53edb131736671f3e69af067e05",
"created_at": 1686101793,
"kind": 1,
"tags": [
[
"e",
"d4af95208a02346338d87b5f4cff7201ddbb16d7c929000819e611192dd8ceee",
"",
"root"
],
[
"e",
"ff17f747a7a2fdf2fc42f2762e92efa6a42193a14764c44f4c61783f817cb3ce",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2011-06-13\n🗒️ Summary of this message: DNS bootstrapping can be made more robust by hosting seeds on services like Zerigo and small VPS, and using namecoin's TLDs to avoid centralization. A simple DNS server build and script can be published for anyone to host, and seeds can be hardcoded or conventionally pointed to bitcoin.* domains. However, there may be concerns about potential attacks from poisoned seeds.\n📝 Original message:Jeff is absolutely correct, stating that DNS bootstrapping can\npotentially be very robust.\n\nConsider, for example, that seeds can be hosted by services like\nzerigo, who provide decent management API's, as well as by thousands\nof small VPS operated by people all over the world. Moreover, if\nnamecoin lives up to it's promises than some seeds can be hosted using\nit's tlds, and as such we would get around centralised ICANN/registrar\nweakness.\n\nThe most practical way I see how to improve DNS bootstrapping is\npublishing build instructions for a simple DNS server build and a\nscript which feeds it with node data. Something simple like djbdns plus\na perl script, or similar zerigo API script, would do. Than anyone can\nhost it. All left to do than is to hardcode a bunch of such DNS seeds\ninto the client.\n\nHardcoding seeds is not good enough? Get a convention that anyone\nowning a bitcoin.* domain should point seed.bitcoin.* to a decent DNS\nseed. Than clients simply scan 100-200 tld's to find working\nseed.bitcoin.*\n\nI am not quite sure, though, is if this would enable some attacks by\npoisoned seeds.\n\nVladimir.",
"sig": "fd66464af850ccd7ae23249e3753af46ee07071b8ae73e9a2488962dadc4a7e27b48e06fe7cda232a594d479344761f1fd959c2dc567387245ee1a77b6a00728"
}