DNS seed "seed.bitcoinstats.com" doesn't support filtering while the comments says it does #29911
Comments
|
I guess I should add that I don't think the nodes returned by "seed.bitcoinstats.com" are good. My assumptions is that it's just caching all the nodes it's previously seen and not checking if they're still providing all the services it previously has. |
|
cc @cdecker |
Indeed, I am checking the infrastructure now. And it.look like the crawler died. I'll see if I can get it back with reasonable effort. |
I have stopped using these DNS seeds. I found only 2 useful when I last tested: seed.bitcoin.sipa.be |
seed.bitcoinstats.com doesn't respect filter requests even though it's advertised as it does. Plus it often returns nodes that are unreachable. In my testing over the past week, it's been the most unreliable dns seed and since we have plenty of mainnet seeds, it's better to do away with this. I documented my findings for this in a Bitcoin Core issue: bitcoin/bitcoin#29911
* chaincfg: remove unresponsive dnsseed on testnet testnet-seed.bitcoin.schildbach.de is unresponsive and doesn't return any ips. Bitcoin Core has already removed it and we don't also be getting rid of it as well. * chaincfg: add dnsseeds from Sjors Provoost His seeds work well and we don't have any for signet and it's good to replace the lost dns seed on testnet. * chaincfg: remove bad dnsseed (seed.bitcoinstats.com) seed.bitcoinstats.com doesn't respect filter requests even though it's advertised as it does. Plus it often returns nodes that are unreachable. In my testing over the past week, it's been the most unreliable dns seed and since we have plenty of mainnet seeds, it's better to do away with this. I documented my findings for this in a Bitcoin Core issue: bitcoin/bitcoin#29911 * chaincfg: add dnsseed from wiz It's the same infrastructure that mempool . space runs on and has been reliable. The same seed is also included in Bitcoin Core as well.
|
yea seeds resolve to nothing, almost 80% nodes are down |
Seeds are up but the results are down? Can't do anything they are hardcoded forever. Do not use them. |
I'm not sure the overall situation is that bad. It looks like at all times, at least two thirds of DNS seeds are returning ~70-99% reachable nodes. Individual seeds/seeders have issues on occasion, but that's not really a problem if they're fixed eventually. Since I'm monitoring the seeds anyway, I can set up some sort of alerting if that helps. |
These have a very low TTL set, which is fine. The DNS seeds using the DNSSEC setup sipa/bitcoin-seeder#85 will renew the DNS zone every hour and have a TTL of 1h set. The DNS seeder https://github.com/sipa/bitcoin-seeder is only providing long running Bitcoin nodes. So caching for one hour is not an issue. |
Is there an existing issue for this?
Current behaviour
It's stated in
chainparams.cppthat "seed.bitcoinstats.com" supports filtering. However, this isn't true.bitcoin/src/kernel/chainparams.cpp
Line 137 in c05c214
Expected behaviour
Since "seed.bitcoinstats.com" supports filtering for
NODE_NETWORK, when asked forNODE_NETWORK, it should return archival nodes. It doesn't.Steps to reproduce
dig x1.seed.bitcoinstats.com.Of the returned addresses, these address do not support
NODE_NETWORKOne can easily check bitnodes data: https://bitnodes.io/nodes/3.8.38.104-8333/
A handful of the nodes here were also unreachable at the time of this writing.
Relevant log output
No response
How did you obtain Bitcoin Core
Pre-built binaries
What version of Bitcoin Core are you using?
v23.0.0 but this doesn't matter here
Operating system and version
Also doesn't matter
Machine specifications
I don't think this matters for this issue
The text was updated successfully, but these errors were encountered: