{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-05-19\n📝 Original message:On Mon, May 19, 2014 at 4:36 PM, Robert McKay \u003crobert at mckay.com\u003e wrote:\n\u003e It should be possible to configure bind as a DNS forwarder.. this can\n\u003e be done in a zone context.. then you can forward the different zones to\n\u003e different dnsseed daemons running on different non-public IPs or two\n\u003e different ports on the same IP (or on one single non-public IP since\n\u003e there's really no reason to expose the dnsseed directly daemon at all).\n\nQuite the opposite.  dnsseed data rotates through a lot of addresses\nif available.  Using the bind/zone-xfer system would result in fewer\ntotal addresses going through to the clients, thanks to the addition\nof caching levels that the bind/zone-xfer system brings.\n\nThat said, if the choice is between no-service and bind, bind it is ;p\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc.      https://bitpay.com/"}