bitmark-DNS-seeder: A C++ repository from dbkeys

bitmark-seeder
==============

Bitmark-seeder is a crawler for the Bitmark network, which exposes a list
of reliable nodes via a built-in DNS server.

Features:
* regularly revisits known nodes to check their availability
* bans nodes after enough failures, or bad behaviour
* accepts nodes down to v0.3.19 to request new IP addresses from,
  but only reports good post-v0.3.24 nodes.
* keeps statistics over (exponential) windows of 2 hours, 8 hours,
  1 day and 1 week, to base decisions on.
* very low memory (a few tens of megabytes) and cpu requirements.
* crawlers run in parallel (by default 24 threads simultaneously).

        This seeder is based on the bitcoin seeder.
        Many thanks, Peter Wuille !

REQUIREMENTS
------------

$ sudo apt-get install build-essential libboost-all-dev libssl-dev

USAGE
-----

Assuming you want to run a dns seed on dnsseed.example.com, you will
need an authorative NS record in example.com's domain record, pointing
to for example vps.example.com:

$ dig -t NS dnsseed.example.com

;; ANSWER SECTION
dnsseed.example.com.   86400    IN      NS     vps.example.com.

On the system vps.example.com, you can now run dnsseed:

./dnsseed -h dnsseed.example.com -n vps.example.com

If you want the DNS server to report SOA records, please provide an
e-mail address (with the @ part replaced by .) using -m.

COMPILING
---------
Compiling will require boost and ssl.  On debian systems, these are provided
by `libboost-dev` and `libssl-dev` respectively.

$ make

This will produce the `dnsseed` binary.

$ make -j6

Makes use of extra CPU's to speed compilation

TESTING
-------

It's sometimes useful to test `dnsseed` locally to ensure it's giving good 
output (either as part of development or snity checking). You can inspect
`dnsseed.dump` to inspect all nodes being tracked for crawling, or you can
issue DNS requests directly. Example: 

$ dig @:: -p 15353 dnsseed.example.com                                                           
       ^       ^    ^
       |       |    |__ Should match the host (-h) argument supplied to dnsseed
       |       |
       |       |_______ Port number (example uses the user space port; see below)
       |
       |_______________ Explicitly call the DNS server on localhost
     

RUNNING AS NON-ROOT
-------------------

Typically, you'll need root privileges to listen to port 53 (name service).

One solution is using an iptables rule (Linux only) to redirect it to
a non-privileged port:

$ iptables -t nat -A PREROUTING -p udp --dport 53 -j REDIRECT --to-port 15353

If properly configured, this will allow you to run dnsseed in userspace, using
the -p 15353 option.

Another solution is allowing binary to bind to ports < 1024 with setcap (IPv6 access-safe)

$ setcap 'cap_net_bind_service=+ep' /path/to/dnsseed


UBUNTU
------
Recent Ubuntu versions have a DNS stub resolver with takes over port 53, and
stops seeder from seeing and answering queries. You must either de-activate the Ubuntu 
stub resolver (systemd-resolved) or redirect external DNS quersies to a non-standard port: 

    dnsseed.MARKS -h <sub-domain.domain.tld> -n <ip-address> -p 5353 -m <admin@email.com>

and configure seeder to answer queries on that port:

   srcPort=53
   dstPort=5353
   iptables -t nat -A PREROUTING -i eth0 -p tcp --dport $srcPort -j REDIRECT --to-port $dstPort
   iptables -t nat -A PREROUTING -i eth0 -p udp --dport $srcPort -j REDIRECT --to-port $dstPort


DISPLAY
-------

Note that the parallel branch, 'ncurses' makes use of the ncurses library to present a more organized display.
dbkeys/bitmark-DNS-seeder
