Print Page - DNS Seeder - Ubuntu - Server setup - bind9

I would like to setup sipa’s Bitcoin Seeder https://github.com/sipa/bitcoin-seeder on my VPS.

I have setup the VPS from scratch and configured bind so that the server is reachable via a FQDN however, I am stuck (like many other people) on how to configure the bind files for the dnsseed.example.com.

In sipa’s Bitcoin Seeder README it shows the following:

Quote

$ 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...

and in another topic somebody mentions:

Quote

the ' vps.example.com' acts as a nameserver for the zone 'dnsseed.example.com'

The zone 'dnsseed.example.com' is handled by the dnsseed program that you have to run on the vps.example.com host. Of course, you also need the A resource record to map vps.example.com to its IP address.

I tried to follow this guide:

https://bitcointalk.org/index.php?topic=599623.0 - Topic: A Basic Guide/Tutorial for Creating DNS Seeders

However, this guide uses a web interface to create the NS and A records. Most VPS are just CLI server box's where DNS needs to be configured using bind.

After searching endlessly and just going around in circles.

Would somebody please post here a working example of the bind files needed to configure a server for this.?

e.g.

db.dnsseed.example.com

;
; BIND data file for local loopback interface
;
$TTL   604800
@   IN   SOA   dnsseed.example.com. root.dnsseed.example.com. (
          3      ; Serial
          604800      ; Refresh
          86400      ; Retry
         2419200      ; Expire
          604800 )   ; Negative Cache TTL
;
@   86400   IN   NS   vps.example.com.
@   IN   A   157.88.166.77
www   IN   A   157.88.166.77
vps   IN   A   157.88.166.77

named.conf.local

//
// Do any local configuration here
//

// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";

zone "dnsseed.example.com" {
   type master;
   file "/etc/bind/db.dnsseed.example.com";
};

named.conf.options

options {
   directory "/var/cache/bind";

   forwarders {
      8.8.8.8;
      8.8.8.4;
   };

   dnssec-validation auto;

   auth-nxdomain no; # conform to RFC1035
   listen-on-v6 { any; };
};

Thanks in advance. My head hurts from this..

I realize this is an old thread, but no answer was ever given to this problem. And unless I am overlooking something here, I would strongly suggest that you do not use bind9 for your DNS seeder setup and instead take advantage of the built-in DNS server offered by the seeder app itself.

I would also like 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

Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: bigbrother1984 on February 15, 2018, 05:09:53 PM