📅 Original date posted:2014-05-19
📝 Original message:On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:
> On Mon, May 19, 2014 at 4:36 PM, Robert McKay <robert at mckay.com>
> wrote:
>> It should be possible to configure bind as a DNS forwarder.. this
>> can
>> be done in a zone context.. then you can forward the different zones
>> to
>> different dnsseed daemons running on different non-public IPs or two
>> different ports on the same IP (or on one single non-public IP since
>> there's really no reason to expose the dnsseed directly daemon at
>> all).
>
> Quite the opposite. dnsseed data rotates through a lot of addresses
> if available. Using the bind/zone-xfer system would result in fewer
> total addresses going through to the clients, thanks to the addition
> of caching levels that the bind/zone-xfer system brings.
>
> That said, if the choice is between no-service and bind, bind it is
> ;p
Setting it up as a zone forwarder causes each request to go through to
the dnsseed backend for each request.
Rob
Robert McKay [ARCHIVE] /
npub1t6…he2py
2023-06-07 15:21:26
in reply to nevent1q…zs7e
Author Public Key
npub1t6suh64e65qzzjtthffl6sa3cagp6k9usnx4qev4jsjzf7xud8psdhe2pyPublished at
2023-06-07 15:21:26Event JSON
{
"id": "09ca1aca9b3c2699f3d0071cda37330cbe638ef8f95aea035b36db883a647755",
"pubkey": "5ea1cbeab9d50021496bba53fd43b1c7501d58bc84cd506595942424f8dc69c3",
"created_at": 1686151286,
"kind": 1,
"tags": [
[
"e",
"27f2cc162bf57c487222b138d4571ce221ca7cd25d269ba16d303b1b70b76927",
"",
"root"
],
[
"e",
"fb03b93449d1bf19038c6e9f219b8ae20e56f3370431999eaf77813d28808bee",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2014-05-19\n📝 Original message:On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:\n\u003e On Mon, May 19, 2014 at 4:36 PM, Robert McKay \u003crobert at mckay.com\u003e \n\u003e wrote:\n\u003e\u003e It should be possible to configure bind as a DNS forwarder.. this \n\u003e\u003e can\n\u003e\u003e be done in a zone context.. then you can forward the different zones \n\u003e\u003e to\n\u003e\u003e different dnsseed daemons running on different non-public IPs or two\n\u003e\u003e different ports on the same IP (or on one single non-public IP since\n\u003e\u003e there's really no reason to expose the dnsseed directly daemon at \n\u003e\u003e all).\n\u003e\n\u003e Quite the opposite. dnsseed data rotates through a lot of addresses\n\u003e if available. Using the bind/zone-xfer system would result in fewer\n\u003e total addresses going through to the clients, thanks to the addition\n\u003e of caching levels that the bind/zone-xfer system brings.\n\u003e\n\u003e That said, if the choice is between no-service and bind, bind it is \n\u003e ;p\n\nSetting it up as a zone forwarder causes each request to go through to \nthe dnsseed backend for each request.\n\nRob",
"sig": "dc849a45069a4579bc58c32f9a65eff1459a62adf123e9dfd2cbe48a04b2ed3945efe2973dcd45c73345d2da56c3bcf0c5a8f54053add3e2001b07dda0baa9ca"
}