Run Hush DNS Seed #3

Open
opened 3 years ago by duke · 1 comments
duke commented 3 years ago
Owner

Running a HUSH DNS seed is similar in resources to running a wormhole: very little disk space and very little bandwidth.

You cannot run a HUSH DNS seed and a Hush full node on the same server, without changing the default port of the Hush full node. A Hush DNS seed pretends to be a HUSH full node, so it must listen on the port full nodes use by default.

DNS Seeds use port 53 (DNS), so usually require firewall/VPN changes, and so DNS seeds require more CLI/Linux/networking knowledge than running an SDL or Wormhole server.

Bounty: 250 HUSH per month
Slots: 4 slots available

Running a HUSH DNS seed is similar in resources to running a wormhole: very little disk space and very little bandwidth. You cannot run a HUSH DNS seed and a Hush full node on the same server, without changing the default port of the Hush full node. A Hush DNS seed pretends to be a HUSH full node, so it must listen on the port full nodes use by default. DNS Seeds use port 53 (DNS), so usually require firewall/VPN changes, and so DNS seeds require more CLI/Linux/networking knowledge than running an SDL or Wormhole server. Bounty: 250 HUSH per month Slots: 4 slots available
Poster
Owner

This task is currently blocked on having a new working DNS seed code which can speak TLS1.3. Our old DNS seeds only speak plaintext and are incompatible with our current network

This task is currently blocked on having a new working DNS seed code which can speak TLS1.3. Our old DNS seeds only speak plaintext and are incompatible with our current network
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.