<p>This appears to be resolved for me in v0.21 with this merged <a href="https://github.com/bitcoin/bitcoin/pull/16939" rel="nofollow noreferrer">PR 16939</a> and some additional context in this <a href="https://github.com/bitcoin/bitcoin/issues/15434" rel="nofollow noreferrer">issue</a> and this Bitcoin Core PR <a href="https://bitcoincore.reviews/16939" rel="nofollow noreferrer">review club</a>.</p>
<p>Falling back to load IP addresses from DNS seeds should be the last resort and as you say addresses of previous peers should be persisted in addrman after stopping bitcoind and restarting.</p>

CC BY-SA 4.0
2021-02-13T13:02:26.200Z
2021-02-13T13:02:26.200Z
Michael Folkson
<p>I stop one of my Bitcoin Core full nodes (v0.19.1) with 10 connections and then start it again. It needs to load IP addresses from DNS seeds. Why is this? Why doesn't it try the addresses of peers it was connected to prior to the shut down? Are they not persisted in addrman? It could then obtain more IP addresses through gossiping from those peers and not need to keep going back to the DNS seeds.</p>

CC BY-SA 4.0
2021-01-19T14:43:44.397Z
I found this https://github.com/bitcoin/bitcoin/pull/16939 and this https://github.com/bitcoin/bitcoin/issues/15434 but will look into more before attempting an answer.
Michael Folkson
CC BY-SA 4.0
2021-01-19T14:50:00.010Z
And this Bitcoin Core PR review club: https://bitcoincore.reviews/16939
Michael Folkson
CC BY-SA 4.0
2021-01-19T16:19:32.650Z
What do you see in the debug.log that indicates it is using the DNS seeds?
Ava Chow
CC BY-SA 4.0
2021-01-19T16:44:15.733Z
"Loading addresses from DNS seed dnsseed.emzy.de" etc followed by the other DNS seeds. Then "277 addresses found from DNS seeds" and "dnsseed thread exit"
Michael Folkson
CC BY-SA 4.0
2021-01-28T01:18:26.177Z
Do you have the same problem with v0.21.0?
Pieter Wuille
CC BY-SA 4.0
2021-02-13T12:57:40.460Z
No I haven't been able to replicate on v0.21.0
Michael Folkson
<bitcoin-core-development><p2p><dns><ip-address>
Why does my full node need to load IP addresses from DNS seeds on restart?
Michael Folkson
# Why does my full node need to load IP addresses from DNS seeds on restart?

(Asked by: username_0 on 2021-01-19)

I stop one of my Bitcoin Core full nodes (v0.19.1) with 10 connections and then start it again. It needs to load IP addresses from DNS seeds. Why is this? Why doesn't it try the addresses of peers it was connected to prior to the shut down? Are they not persisted in addrman? It could then obtain more IP addresses through gossiping from those peers and not need to keep going back to the DNS seeds.

**Tags:** bitcoin-core-development, p2p, dns, ip-address

> **Comments:**
> **username_0**: I found this https://github.com/bitcoin/bitcoin/pull/16939 and this https://github.com/bitcoin/bitcoin/issues/15434 but will look into more before attempting an answer.  
> **username_0**: And this Bitcoin Core PR review club: https://bitcoincore.reviews/16939  
> **username_1**: What do you see in the debug.log that indicates it is using the DNS seeds?  
> **username_0**: "Loading addresses from DNS seed dnsseed.emzy.de" etc followed by the other DNS seeds. Then "277 addresses found from DNS seeds" and "dnsseed thread exit"  
> **username_2**: Do you have the same problem with v0.21.0?  
> **username_0**: No I haven't been able to replicate on v0.21.0  

---

## 1 answers

### Answer by username_0 on 2021-02-13. Score: 2 | Accepted answer

This appears to be resolved for me in v0.21 with this merged [PR 16939](https://github.com/bitcoin/bitcoin/pull/16939) and some additional context in this [issue](https://github.com/bitcoin/bitcoin/issues/15434) and this Bitcoin Core PR [review club](https://bitcoincore.reviews/16939).

Falling back to load IP addresses from DNS seeds should be the last resort and as you say addresses of previous peers should be persisted in addrman after stopping bitcoind and restarting.


---

