I realize this is an old thread, but it seems that even to this day people still struggle with setting up DNS seeders for their altcoins. It's difficult to say what the OP's problem was, but I'm leaning very heavily to it being a missing magic variable in the source code that wasn't changed to match the altcoins network.
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://bitcointalksearch.org/topic/dns-seeder-setup-guide-using-the-generic-seeder-5239304
Topic: dnsseder setup (Read 363 times)
Hello,
Troubleshooting a dnsseed installation is somewhat difficult because there is more to it than just adapting the code.
You're going to need to be answering requests on port 53.
You're going to need to have the NS record in Global DNS referring to the hostname of the system where dnsseed runs.
You're going to need to have the configured name of the nameserver matching in the parent zone.
If you've configured a dnsseed to run on ns.foocoin.test with the zone named dnsseed.foocoin.test, then you can test it with a remote connection by doing a 'dig @ns.foocoin.test dnsseed.foocoin.test'.
You can also check the debug.log of a hard coded seed to see if bitcoin-seeder is crawling properly.
What are you seeing exactly?
Best Regards,
-Chicago
Troubleshooting a dnsseed installation is somewhat difficult because there is more to it than just adapting the code.
You're going to need to be answering requests on port 53.
You're going to need to have the NS record in Global DNS referring to the hostname of the system where dnsseed runs.
You're going to need to have the configured name of the nameserver matching in the parent zone.
If you've configured a dnsseed to run on ns.foocoin.test with the zone named dnsseed.foocoin.test, then you can test it with a remote connection by doing a 'dig @ns.foocoin.test dnsseed.foocoin.test'.
You can also check the debug.log of a hard coded seed to see if bitcoin-seeder is crawling properly.
What are you seeing exactly?
Best Regards,
-Chicago
Hello,
i recently received nice help here, so hopefully you can also help me here
I am trying to setup this dnsseeder here: https://bitcointalksearch.org/topic/m.6598209
I am very sure i have setup right "message start/magic packet" stuff things. Ports should also be fine.
I have a NS and A record includeing "www" for node.coin.com
I have a node and the dnsseder running on the same machine, but it is not getting any connections.
I have put all active nodes from explorer into it but it wont show any active connections.
I hope you can help me
i recently received nice help here, so hopefully you can also help me here
I am trying to setup this dnsseeder here: https://bitcointalksearch.org/topic/m.6598209
I am very sure i have setup right "message start/magic packet" stuff things. Ports should also be fine.
I have a NS and A record includeing "www" for node.coin.com
I have a node and the dnsseder running on the same machine, but it is not getting any connections.
I have put all active nodes from explorer into it but it wont show any active connections.
I hope you can help me
Jump to: