Bitcoin Core does not immediately use the fixed seed nodes if DNS seeding is disabled (-dnsseed=0) #19795

issue practicalswift opened this issue on August 24, 2020
  1. practicalswift commented at 10:03 PM on August 24, 2020: contributor

    Expected behavior: Disabling DNS seeding (-dnsseed=0) should make Bitcoin Core use the fixed seed nodes immediately on startup (assuming an empty peers.dat).

    Actual behavior: The fixed seed nodes are used but only after an unnecessary 60 second timeout, and a somewhat misleading log message ("Adding fixed seed nodes as DNS doesn't seem to be available.").

    To reproduce: rm ~/.bitcoin/peers.dat && src/bitcoind -dnsseed=0 and wait... 💤

    This issue is probably a "good first issue" :)

  2. practicalswift added the label Bug on Aug 24, 2020
  3. dhruv commented at 2:45 AM on August 25, 2020: contributor

    I'll try to work on this and report back.

  4. practicalswift commented at 5:14 AM on August 25, 2020: contributor

    @dhruv That's great! Don't hesitate to ping me when you're ready for review :)

  5. laanwj added the label P2P on Sep 3, 2020
  6. laanwj removed the label Bug on Sep 3, 2020
  7. dhruv cross-referenced this on Sep 5, 2020 from issue p2p: No delay in adding fixed seeds if -dnsseed=0 and peers.dat is empty by dhruv
  8. laanwj closed this on Feb 12, 2021
  9. sidhujag referenced this in commit 255abc22a9 on Feb 12, 2021
  10. Sjors cross-referenced this on May 22, 2021 from issue net: ignore block-relay-only peers when skipping DNS seed by ajtowns
  11. bitcoin locked this on Aug 18, 2022
Contributors
practicalswiftdhruv
Labels
P2P
Linked (view graph)
#19884 p2p: No delay in adding fixed seeds if -dnsseed=0 and peers.dat is empty#22013 net: ignore block-relay-only peers when skipping DNS seed
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-20 06:54 UTC