Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chaincfg: update dnsseeds #2174

Merged
merged 4 commits into from Apr 23, 2024

Conversation

kcalvinalvin
Copy link
Collaborator

@kcalvinalvin kcalvinalvin commented Apr 22, 2024

To summarize:

Removed two seeds: testnet-seed.bitcoin.schildbach.de(testnet), seed.bitcoinstats.com(mainnet).

One from schildbach.de is completely unreachable and is also removed in Core. bitcoinstats.com seed is reachable but returns bad results. Documented at bitcoin/bitcoin#29911

Added seeds from Sjors on all three networks.
Added seed from Wiz on mainnet.

I can separate the commits out into different PRs if desired

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.
His seeds work well and we don't have any for signet and it's good to
replace the lost dns seed on testnet.
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
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.
@coveralls
Copy link

Pull Request Test Coverage Report for Build 8789473541

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 1 unchanged line in 1 file lost coverage.
  • Overall coverage increased (+0.004%) to 56.874%

Files with Coverage Reduction New Missed Lines %
mempool/mempool.go 1 66.84%
Totals Coverage Status
Change from base Build 8636847188: 0.004%
Covered Lines: 29450
Relevant Lines: 51781

💛 - Coveralls

Copy link
Collaborator

@guggero guggero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tACK

seed.bitcoin.sprovoost.nl currently doesn't respond (or gives me a SERVFAIL), but I see that the same domain name is indeed present in Bitcoin Core (and is likely a temporary server failure, cc @Sjors)

@Sjors
Copy link

Sjors commented Apr 23, 2024

@guggero does my seed fail if you test it with this script? https://github.com/bitcoin-core/bitcoin-maintainer-tools/blob/main/check-dnsseeds.py

If not, which dig command did you use? The seed can return IPv4 and IPv6 records and can be reached via IPv4 and IPv6. Is one of there permutations not working, or all of them?

(I'm seeing some issues as well from my end, so looking into it)

Update: mainnet seed should be fixed now

@guggero
Copy link
Collaborator

guggero commented Apr 23, 2024

I just did a dig A seed.bitcoin.sprovoost.nl. That seems to work now, so thanks for the fix!

Copy link
Member

@jcvernaleo jcvernaleo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@jcvernaleo jcvernaleo merged commit f1bded4 into btcsuite:master Apr 23, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants