Bitcoin Forum
December 12, 2024, 12:48:48 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: how to setup dnsseed for altcoin?  (Read 230 times)
olddocks (OP)
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
March 07, 2018, 04:03:17 PM
 #1

I am confused setting up nameserver to run with dnsseeder. I modified dnsseeder to work with my new altcoin.

Here is what is did.

I have vps.example.com setup with amazon ec2 and i compiled dnsseeder. I went to godaddy dns settings of my domain example.com and added my 1.2.3.4 (elastic public ip)

Hostname in Godaddy

vps.example.com  mapped to 1.2.3.4
and the nameservers in godaddy domain are like this

Code:
Type    Name    Value   TTL Actions
A   @   1.2.3.4              1 Hour
NS  @   ns27.domaincontrol.com  1 Hour  
NS  @   ns28.domaincontrol.com  1 Hour  
NS  dnsseed vps.example.com 1 Hour

This way dnsseed.example.com points to vps.example.com (this is my hostname where i run dnsseeder)

Then i run dnsseeder

Code:
./dnsseed -h dnsseed.example.com -n vps.example.com -m root.example.com

Code:
Supporting whitelisted filters: 0x1,0x5,0x9,0xd
Loading dnsseed.dat...done
Starting 4 DNS threads for dnsseed.citizenshipcoin.org on vps.citizenshipcoin.org (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
                                                                                                          [18-03-07 00:49:14] 0/1                                                                                   [18-03-07 00:49:15] 0/1 available (1 tried in 2s                                                          [18-03-07 00:49:16] 0/1 available (1 tried in 3s, 0 new, 0 active), 0 ba                                  [18-03-07 00:49:17] 0/1 available (1 tried in 4s, 0 new, 0 active), 0 banned; 0 DNS requests, 0  
when i query nslook, it is not returning any dns ips.

Code:
$ dig -t NS dnsseed.example.com

; <<>> DiG 9.7.3 <<>> -t NS dnsseed.example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44679
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;dnsseed.example.com.   IN  NS

;; Query time: 1554 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Mar  7 01:40:44 2018
;; MSG SIZE  rcvd: 45

It seems something is wrong. I am supposed to receive multiple set of IPs as answer.

What did i do wrong?

|SharpShooter|
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
March 08, 2018, 11:41:19 PM
 #2

I am confused setting up nameserver to run with dnsseeder. I modified dnsseeder to work with my new altcoin.

Here is what is did.

I have vps.example.com setup with amazon ec2 and i compiled dnsseeder. I went to godaddy dns settings of my domain example.com and added my 1.2.3.4 (elastic public ip)

Hostname in Godaddy

vps.example.com  mapped to 1.2.3.4
and the nameservers in godaddy domain are like this

Code:
Type    Name    Value   TTL Actions
A   @   1.2.3.4              1 Hour
NS  @   ns27.domaincontrol.com  1 Hour  
NS  @   ns28.domaincontrol.com  1 Hour  
NS  dnsseed vps.example.com 1 Hour

This way dnsseed.example.com points to vps.example.com (this is my hostname where i run dnsseeder)

Then i run dnsseeder

Code:
./dnsseed -h dnsseed.example.com -n vps.example.com -m root.example.com

Code:
Supporting whitelisted filters: 0x1,0x5,0x9,0xd
Loading dnsseed.dat...done
Starting 4 DNS threads for dnsseed.citizenshipcoin.org on vps.citizenshipcoin.org (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
                                                                                                          [18-03-07 00:49:14] 0/1                                                                                   [18-03-07 00:49:15] 0/1 available (1 tried in 2s                                                          [18-03-07 00:49:16] 0/1 available (1 tried in 3s, 0 new, 0 active), 0 ba                                  [18-03-07 00:49:17] 0/1 available (1 tried in 4s, 0 new, 0 active), 0 banned; 0 DNS requests, 0  
when i query nslook, it is not returning any dns ips.

Code:
$ dig -t NS dnsseed.example.com

; <<>> DiG 9.7.3 <<>> -t NS dnsseed.example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44679
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;dnsseed.example.com.   IN  NS

;; Query time: 1554 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Mar  7 01:40:44 2018
;; MSG SIZE  rcvd: 45

It seems something is wrong. I am supposed to receive multiple set of IPs as answer.

What did i do wrong?



Hi did you get this figured out? Unfortunately i am in the same boat as you and i havent been able to receive a single help from anyone. How did you get your vps.example.com added to godaddy? It didnt let me do that.
skaleita
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
July 02, 2018, 07:34:28 AM
 #3

I am confused setting up nameserver to run with dnsseeder. I modified dnsseeder to work with my new altcoin.

Here is what is did.

I have vps.example.com setup with amazon ec2 and i compiled dnsseeder. I went to godaddy dns settings of my domain example.com and added my 1.2.3.4 (elastic public ip)

Hostname in Godaddy

vps.example.com  mapped to 1.2.3.4
and the nameservers in godaddy domain are like this

Code:
Type    Name    Value   TTL Actions
A   @   1.2.3.4              1 Hour
NS  @   ns27.domaincontrol.com  1 Hour  
NS  @   ns28.domaincontrol.com  1 Hour  
NS  dnsseed vps.example.com 1 Hour

This way dnsseed.example.com points to vps.example.com (this is my hostname where i run dnsseeder)

Then i run dnsseeder

Code:
./dnsseed -h dnsseed.example.com -n vps.example.com -m root.example.com

Code:
Supporting whitelisted filters: 0x1,0x5,0x9,0xd
Loading dnsseed.dat...done
Starting 4 DNS threads for dnsseed.citizenshipcoin.org on vps.citizenshipcoin.org (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
                                                                                                          [18-03-07 00:49:14] 0/1                                                                                   [18-03-07 00:49:15] 0/1 available (1 tried in 2s                                                          [18-03-07 00:49:16] 0/1 available (1 tried in 3s, 0 new, 0 active), 0 ba                                  [18-03-07 00:49:17] 0/1 available (1 tried in 4s, 0 new, 0 active), 0 banned; 0 DNS requests, 0  
when i query nslook, it is not returning any dns ips.

Code:
$ dig -t NS dnsseed.example.com

; <<>> DiG 9.7.3 <<>> -t NS dnsseed.example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44679
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;dnsseed.example.com.   IN  NS

;; Query time: 1554 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Mar  7 01:40:44 2018
;; MSG SIZE  rcvd: 45

It seems something is wrong. I am supposed to receive multiple set of IPs as answer.

What did i do wrong?



Hi did you get this figured out? Unfortunately i am in the same boat as you and i havent been able to receive a single help from anyone. How did you get your vps.example.com added to godaddy? It didnt let me do that.


can anyone shead some light on this, im running into the same problem, everythings set up right on the godaddy end but im getting this



Starting 4 DNS threads for dnsseed.example.com on dns.example.com (port 53).......done
Starting seeder...done
Starting 96 crawler threads...done
[18-07-02 08:33:32] 0/2 available (2 tried in 153s, 0 new, 0 active), 0 banned; 0 DNS requests, 0 db queries
joe@exor
Jr. Member
*
Offline Offline

Activity: 43
Merit: 16


View Profile WWW
May 07, 2020, 07:07:42 PM
 #4

Without more details, it's difficult to tell if some of the issues described in this thread were caused by improper DNS setup and/or if some magic values in the source code were not properly updated for use with a different altcoin. I just want to point out that nowadays there is a clone of the bitcoin-seeder called the generic-seeder that is much easier to setup for most altcoins and also includes a step-by-step setup guide for all parts of the process. It adds new optional features, some small fixes and most importantly, you no longer have to edit the source code to get it to work with your altcoin because all the common variables that change across altcoins have been separated into a config file for easy configuration.

Read more here: https://bitcointalk.org/index.php?topic=5239304.0
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!