Help with DNS Seeder and hardcoded Seednodes

[12sided-dice]

I am not running a wallet on cryptodistributed.org.

Do you mean that I should be running an instance of the coin daemon on 104.131.53.44? If this is the case I definitely did not understand that to be so.

[bee7]

I am not running a wallet on cryptodistributed.org.

Do you mean that I should be running an instance of the coin daemon on 104.131.53.44? If this is the case I definitely did not understand that to be so.

You should be running the instance of your coin wallet at cryptodistributed.org as your dnsseed has this address encoded as an address of a seed node.
The dnsseed then collect the list of known to this node peers form it and publish it through dns.

Edit: This is not correct.

[bigreddmachine]

104.131.18.228 is the IP address of my seednode as is configured as follows;

unsigned int pnSeed[] =
{
      0x688312e4
};

I am fairly certain this is your problem.  I believe that you have to reverse the IP address, so your pnSeed should be 0xe4128368.

Here is a perl script I found that will do this for you:

Code:

#!/usr/bin/perl

# Twobits twobit integer dotted quad to reverse hex convertor
#  designed for q&d use to put seeds into pnSeeds in *coins

my $ip;

if (@ARGV) {
    $ip = shift @ARGV;
} else {
    print "Enter an (dotted quad) ip address: ";
    chomp( $ip = <STDIN> );
}

printf "0x%08x\n",  unpack 'N', pack 'C4', reverse split '\.', $ip;

I got that from this Bitcointalk comment by twobits:
https://bitcointalk.org/index.php?topic=34586.msg1983185#msg1983185

[12sided-dice]

Thank you bigredmachine! that was exactly the mistake I've been struggling with.  Clients are now able to connect to the seednode and subsequently to other clients.  I can't offer much but pm me and it would be my pleasure to buy you a beer.

Cannot connect to kjy2eqzk4zwi5zd3.onion:9751: unsupported network

Are you running Tor? And have you put up a hidden service at port 9751 on that node?

I am not running Tor. The coin daemon attempts this connection automatically.

You should be running the instance of your coin wallet at cryptodistributed.org as your dnsseed has this address encoded as an address of a seed node.
The dnsseed then collect the list of known to this node peers form it and publish it through dns.

I am now running an instance of the coin daemon on vps 104.131.53.44 and am still unable to connect to peers using DNS.

I get the following:

Code:

dnsseed thread start
Loading addresses from DNS seeds (could take a while)
addcon thread start
msghand thread start
opencon thread start
net thread start
dumpaddr thread start
init message: Done loading
0 addresses found from DNS seeds
dnsseed thread exit
GetMyExternalIP() received [104.131.18.112] 104.131.18.112:0
GetMyExternalIP() returned 104.131.18.112
AddLocal(104.131.18.112:9751,4)
ext-ip thread exit
Adding fixed seed nodes as DNS doesn't seem to be available.

The DNS seeder shows nothing:

Code:

$ 0/1 available (1 tried in 800s, 0 new, 0 active), 0 banned; 0 DNS requests, 4 db queries

Something is definitely wrong with my current DNS configuration. I have a hunch it has to do with an improperly configured reverse zone file. 

I came across this stackoverflow as a possible solution, but I have not been able to find any posts within the cryptocurrency community where this solution was necessary. I'm not sure it will even be of use in this situation.
http://stackoverflow.com/questions/15338232/how-to-forward-a-subzone

[bee7]

@OP, check PM, please

[12sided-dice]

Thanks to bee7 and bigredmachine pnSeeds and the dns seeder are properly functioning. Solutions will be posted in OP.

[bigreddmachine]

Thanks to bee7 and bigredmachine pnSeeds and the dns seeder are properly functioning. Solutions will be posted in OP.

No worries!  It would be awesome if you made a good addition to the post with all the solutions (keep the original question and just add the answer, so that others in the future can search and find it!).

[bhokor]

Hi guys, i am trying to run a dns seeder, all works fine thank to this great tutorial except one thing, the dns dnsseed only get the peers that use the default p2p port and discard all of them who uses another ports, there are some way to avoid

thanks very much in advance

[joe@exor]

I realize this is an extremely old post, but it seems that even to this day people still struggle with setting up DNS seeders for their altcoins. 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