gombadi / dnsseeder Goto Github PK

At least Google's Public DNS servers and tor-resolve (Tor SOCKS5 implementation) is incompatible with servers running this dnsseeder.

Google's Public DNS servers used to work fine, but recently stopped doing so - users get a no records found message, like inexistent name, when in fact a local unbound daemon will get the records just fine.

Maybe blocked by: #18
It must be a particularity of this software, because the dnsseeds that run different software work with Google public DNS just fine, so the length / size of the response (many AAAA and A records) are NOT the issue.

Would PR's be accepted that add config files for networks other than Bitcoin and Twister? (I'm considering sending in a PR that adds Namecoin.)

It would be useful for the README.md to document how DNS is supposed to be set up. My assumption here is that it looks something like the following:

1. Run the seeder on a machine whose IP is accessible via seeder-backend.example.org.
2. Put an NS record at seeder.example.org pointing to seeder-backend.example.org..
3. Use seeder.example.org as the DNS seed in a Bitcoin client.

But it took me a few minutes to figure out that this was the likely setup procedure, and I suspect it's non-obvious to a significant set of people.

Is there any reason why dnsseeder doesn't use the btcd/peer package for its connections to the P2P network? Seems like doing so might avoid duplicating code between btcd and dnsseeder.

Error when I try to crawl custom network

It would be helpful if the seeder returned an NS record, corresponding to the domain name where the seeder is running. This would enable stuff like dig NS seed.namecoin.libreisp.se to work correctly.

This dnsseeder implementation is missing a major feature of sipa's dnsseeder. Filtering by service bits.
Thex49service bit shows that a node supports NODE_NETWORK | NODE_WITNESS | NODE_COMPACT_FILTERS, and this could be requested like this:

$ nslookup x49.seed.bitcoin.sprovoost.nl
Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
Name:	x49.seed.bitcoin.sprovoost.nl
Address: 142.166.19.23
Name:	x49.seed.bitcoin.sprovoost.nl
Address: 2.238.146.172
Name:	x49.seed.bitcoin.sprovoost.nl
Address: 217.123.106.211
Name:	x49.seed.bitcoin.sprovoost.nl
Address: 5.157.103.202

It would be useful to support a SOCKSv5 proxy (e.g. Tor) for the P2P connections.