To avoid issues with DNS blacklisting, I've setup a separate domain for my DNS seed.
(This time, without a potentially alarming name)
To avoid issues with DNS blacklisting, I've setup a separate domain for my DNS seed.
(This time, without a potentially alarming name)
To avoid issues with DNS blacklisting, I've setup a separate domain for my DNS seed.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | petertodd, mzumsande, fanquake |
| Concept ACK | Sjors, kevkevinpal |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Concept ACK, seems like a fine name. Haven't tested yet.
Concept ACK 4f273ab, name looks good to me
ACK https://github.com/bitcoin/bitcoin/pull/29691/commits/4f273ab4360c9aa72c2feb78787e1811ab58dc16
DNS seems to resolve just fine for me, and returns IP addresses with a fair bit of overlap with the ones my DNS seed has.
@luke-jr can you GPG sign this commit?
Someone, possibly you, should also make a PR to update it here: https://github.com/bitcoin-core/bitcoin-maintainer-tools/blob/main/check-dnsseeds.py (better still if it just parses src/kernel/chainparams.cpp).
I ran the above script locally and it's happy.
ACK 4f273ab4360c9aa72c2feb78787e1811ab58dc16
I did a quick check that it returns valid addresses under the new domain.
ACK 4f273ab4360c9aa72c2feb78787e1811ab58dc16
Someone, possibly you, should also make a PR to update it here:
I don't see why the person making the PR there matters; it's only copying what is in kernel/chainparams. Opened one for recent changes: https://github.com/bitcoin-core/bitcoin-maintainer-tools/pull/160