A Basic Guide/Tutorial for Creating DNS Seeders

[hey_connor]

The variable "clientVersion" is compared with REQUIRE_VERSION(which is a protocol version) in the function IsGood,

Code:

if (clientVersion && clientVersion < REQUIRE_VERSION) return false;

while it is compared with 31900(which seems to be a client version v0.3.19) in the function GetBanTime.

Code:

if (clientVersion && clientVersion < 31900) { return 604800; }

What on earth should "clientVersion" be compared with? Client version or protocol version?

[1715131639]

1715131639

[1715131639]

1715131639

[1715131639]

1715131639

[1715131639]

1715131639

[1715131639]

1715131639

[1715131639]

1715131639

[suprnurd]

I believe clientVersion is the protocol version - I believe the seeder is only saving the "protocolversion" from the nodes it connects to and does not do anything with the "version" (i.e. from -getinfo)

If you check you'll see that clientVersion doesn't get overwritten with a different value for each if statement so it will always contain the protocol version.

[Epssos]

Hi,
I'm trying to setup bitcoin seeder, but i'm having problem with correct DNS setup.

Domain is registered in Goddady, and i have DNS record:

Code:

NS               @                   ns1.seederio.com          1h

VPS in Vultr, with IPv6 and reverse DNS

Code:

 xxxxxxxxxxxxxxxxxxxxxxxxxxx	ns1.seederio.com

Command to run seeder (with root priv):

Code:

./dnsseed -h seederio.com -n ns1.seederio.com -m admin@seederio.com -t 2 -d 1

But after command:

Code:

dig -t A ns1.seederio.com

I've got following message:

Code:

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ns1.seederio.com.              IN      A

;; AUTHORITY SECTION:
seederio.com.           600     IN      SOA     ns13.domaincontrol.com. dns.jomax.net. 2019123003 28800 7200 604800 600

;; Query time: 217 msec
;; SERVER: 62.179.1.61#53(62.179.1.61)
;; WHEN: Mon Dec 30 13:15:17 CET 2019
;; MSG SIZE  rcvd: 116

For

Code:

dig -t NS ns1.seederio.com

I've got the same result. Could you help me with this problem?

[suprnurd]

I got it working on my end by using a subdomain so something like this:

Code:

A		ns		111.222.333.444		1h
NS		seeder		ns.seederio.com		1h

dnsseed -h seeder.seederio.com -n ns.seederio.com -m no-reply@seederio.com

dig seeder.seederio.com

;; ANSWER SECTION:
seeder.seederio.com. 3600 IN	A	111.222.333.444
					111.222.333.445
					111.222.333.446

[Epssos]

I got it working on my end by using a subdomain so something like this:

Code:

A		ns		111.222.333.444		1h
NS		seeder		ns.seederio.com		1h

dnsseed -h seeder.seederio.com -n ns.seederio.com -m no-reply@seederio.com

dig seeder.seederio.com

;; ANSWER SECTION:
seeder.seederio.com. 3600 IN	A	111.222.333.444
					111.222.333.445
					111.222.333.446

Still no result. When i put

Code:

dig +trace @8.8.8.8 seeder.seederio.com any

I've got:

Code:

;; Connection to 2001:41d0:xxxxxxxx#53(2001:41d0:xxxxxx) for seeder.seederio.com failed: connection refused.

Seeder is working on port 53. UFW is disable

Code:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1479/sshd
tcp6       0      0 :::22                   :::*                    LISTEN      1479/sshd
udp        0      0 0.0.0.0:68              0.0.0.0:*                           1108/dhclient
udp6       0      0 :::53                   :::*                                10929/dnsseed
root@vps790584:~/seeder# sudo lsof -i -P -n | grep LISTEN
sshd      1479 root    3u  IPv4  14942      0t0  TCP *:22 (LISTEN)
sshd      1479 root    4u  IPv6  14951      0t0  TCP *:22 (LISTEN)

[joe@exor]

Hi,
I'm trying to setup bitcoin seeder, but i'm having problem with correct DNS setup.

Domain is registered in Goddady, and i have DNS record:

Code:

NS               @                   ns1.seederio.com          1h

VPS in Vultr, with IPv6 and reverse DNS

Code:

 xxxxxxxxxxxxxxxxxxxxxxxxxxx	ns1.seederio.com

Command to run seeder (with root priv):

Code:

./dnsseed -h seederio.com -n ns1.seederio.com -m admin@seederio.com -t 2 -d 1

But after command:

Code:

dig -t A ns1.seederio.com

I've got following message:

Code:

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ns1.seederio.com.              IN      A

;; AUTHORITY SECTION:
seederio.com.           600     IN      SOA     ns13.domaincontrol.com. dns.jomax.net. 2019123003 28800 7200 604800 600

;; Query time: 217 msec
;; SERVER: 62.179.1.61#53(62.179.1.61)
;; WHEN: Mon Dec 30 13:15:17 CET 2019
;; MSG SIZE  rcvd: 116

For

Code:

dig -t NS ns1.seederio.com

I've got the same result. Could you help me with this problem?

You are missing some steps in your DNS setup.

First of all, you are required to create both an NS and "A" record, and it looks like you have only created an NS record (and even that I don't think is true because you seem to be trying to use your domains default ns1 nameserver). Next, your NS record must point to the "A" record, and your "A" record must point to the ip address of your vps. And lastly, your arguments for running the seeder app are mixed up a bit.

To correct your current setup I would do something like this:

1) Create an "A" record that points to the ip address for your vps (ex: 111.222.123.231). You can give it any name you want but for this example lets call it vps.seederio.com
2) Create a new NS record and point it to the "A" record you just created. The NS record can also be called whatever you want but for this example lets call it seeder.seederio.com
3) On your vps, setup the DNS seeder app according to the instructions (I believe you already did this step)
4) Run the following cmd on the vps to start crawling your coins network and simultaneously start listening for DNS requests:

Code:

./dnsseed -h seeder.seederio.com -n vps.seederio.com -m email.example.com

5) Wait a few minutes to allow the seeder to find the "good" nodes on your network.
6) You can test that your seeder is working by using the following cmd, but keep in mind that these values can be cached and may not always give a good result even if it is working:

Code:

nslookup seeder.seederio.com

If all is working it should return a list of "good" ip addresses that are valid seed nodes for your network. An alternative to using the nslookup cmd is to use an online service to check if your seeder is working. You can visit this page after your seeder is running to see if it is working (you should see lots of ip addresses and green checkmarks. Seeing no ip addresses and red X's means something isnt working): https://www.whatsmydns.net/#A/seeder.seederio.com

7) That's it! You are done! 

[joe@exor]

I would like to say a BIG THANK YOU to the original creator of this thread @PereguineBerty, as this has served as the main setup guide for the bitcoin-seeder for exactly 6 years to the day!

A lot has changed since then, and earlier this year I took it upon myself to improve the functionality of the seeder app and also took the time to write a complete step-by-step guide for its use.

All details, including a copy of the full guide can be found here: https://bitcointalk.org/index.php?topic=5239304.0