In getfloresta#793 we reduced the `DNS_SEED_REQUEST_INTERVAL` to two minutes.
This tells how long do we wait before re-doing a request do the DNS
seeds. The goal was to make sure we had enough peers to keep going.

However, it doesn't seem like it worked as intended since DNS servers
are currently bad at giving utreexo peers (and on signet they are also
bad at giving CBS peers). This forces our node to retry DNS requests
every two minutes. But since most users don't have their own recursive
resolver (I don't), the previous result is almost always cached, so you
get basically the same answer several times.

This pollutes stdout for no good reason. Since getfloresta#781 we now are super
aggressive about asking for addresses and checking whether they are
alive and learning about their capabilities and getfloresta#865 will make it
even better, since we can try several feeler connections at the same
time. So I think DNS seeds should be only used to get us some starting
peers, and then we build our local network view from the P2P net
ourselves.

In getfloresta#793 we reduced the `DNS_SEED_REQUEST_INTERVAL` to two minutes.
This tells how long do we wait before re-doing a request do the DNS
seeds. The goal was to make sure we had enough peers to keep going.

However, it doesn't seem like it worked as intended since DNS servers
are currently bad at giving utreexo peers (and on signet they are also
bad at giving CBS peers). This forces our node to retry DNS requests
every two minutes. But since most users don't have their own recursive
resolver (I don't), the previous result is almost always cached, so you
get basically the same answer several times.

This pollutes stdout for no good reason. Since getfloresta#781 we now are super
aggressive about asking for addresses and checking whether they are
alive and learning about their capabilities and getfloresta#865 will make it
even better, since we can try several feeler connections at the same
time. So I think DNS seeds should be only used to get us some starting
peers, and then we build our local network view from the P2P net
ourselves.

In getfloresta#793 we reduced the `DNS_SEED_REQUEST_INTERVAL` to two minutes.
This tells how long do we wait before re-doing a request do the DNS
seeds. The goal was to make sure we had enough peers to keep going.

However, it doesn't seem like it worked as intended since DNS servers
are currently bad at giving utreexo peers (and on signet they are also
bad at giving CBS peers). This forces our node to retry DNS requests
every two minutes. But since most users don't have their own recursive
resolver (I don't), the previous result is almost always cached, so you
get basically the same answer several times.

This pollutes stdout for no good reason. Since getfloresta#781 we now are super
aggressive about asking for addresses and checking whether they are
alive and learning about their capabilities and getfloresta#865 will make it
even better, since we can try several feeler connections at the same
time. So I think DNS seeds should be only used to get us some starting
peers, and then we build our local network view from the P2P net
ourselves.

In getfloresta#793 we reduced the `DNS_SEED_REQUEST_INTERVAL` to two minutes.
This tells how long do we wait before re-doing a request do the DNS
seeds. The goal was to make sure we had enough peers to keep going.

However, it doesn't seem like it worked as intended since DNS servers
are currently bad at giving utreexo peers (and on signet they are also
bad at giving CBS peers). This forces our node to retry DNS requests
every two minutes. But since most users don't have their own recursive
resolver (I don't), the previous result is almost always cached, so you
get basically the same answer several times.

This pollutes stdout for no good reason. Since getfloresta#781 we now are super
aggressive about asking for addresses and checking whether they are
alive and learning about their capabilities and getfloresta#865 will make it
even better, since we can try several feeler connections at the same
time. So I think DNS seeds should be only used to get us some starting
peers, and then we build our local network view from the P2P net
ourselves.

0ceeb59 chore(wire): increase the dns seed grace period time (Davidson Souza)

Pull request description:

  ### Description and Notes

  In #793 we reduced the `DNS_SEED_REQUEST_INTERVAL` to two minutes.
  This tells how long do we wait before re-doing a request do the DNS
  seeds. The goal was to make sure we had enough peers to keep going.

  However, it doesn't seem like it worked as intended since DNS servers
  are currently bad at giving utreexo peers (and on signet they are also
  bad at giving CBS peers). This forces our node to retry DNS requests
  every two minutes. But since most users don't have their own recursive
  resolver (I don't), the previous result is almost always cached, so you
  get basically the same answer several times.

  This pollutes stdout for no good reason. Since #781 we now are super
  aggressive about asking for addresses and checking whether they are
  alive and learning about their capabilities and #865 will make it
  even better, since we can try several feeler connections at the same
  time. So I think DNS seeds should be only used to get us some starting
  peers, and then we build our local network view from the P2P net
  ourselves.

ACKs for top commit:
  luisschwab:
    ACK 0ceeb59
  JoseSK999:
    ACK 0ceeb59

Tree-SHA512: a3529e147ca18ba18eab7b59918b17521a70addf9de7c37750612e58b6aea9f3173869672454126f516b2e38bd3d7f597d5e3731b850d2b86201982b8e14eae7