Add holesky dns url to supported chains info

[scorbajio]

Also see Holesky DNS Network for Peer Discovery

[codecov]

Codecov Report

Merging #3088 (e45527c) into master (9579e5e) will decrease coverage by 0.79%.
The diff coverage is 100.00%.

Additional details and impacted files

Flag	Coverage Δ
block	88.78% <ø> (ø)
blockchain	92.61% <ø> (ø)
client	?
common	98.19% <100.00%> (+<0.01%)	⬆️
ethash	?
evm	71.87% <ø> (ø)
rlp	?
statemanager	90.23% <ø> (ø)
trie	90.25% <ø> (-0.14%)	⬇️
tx	96.36% <ø> (ø)
util	86.97% <ø> (ø)
vm	76.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[holgerd77]

Rebased this via UI

[holgerd77]

Did you try and test here (e.g. via activating debug logs for devp2p) if DNS connection is going on successfully?

[scorbajio]

Did you try and test here (e.g. via activating debug logs for devp2p) if DNS connection is going on successfully?

Seems to be working as expected:

[10-08|11:31:49] INFO Initializing Ethereumjs client version=v0.8.1 network=holesky chainId=17000 

...

2023-10-08T18:31:50.174Z devp2p:dns:dns got new peer candidate from DNS address=23.124.84.197
2023-10-08T18:31:50.313Z devp2p:dns:dns got new peer candidate from DNS address=194.33.40.147
2023-10-08T18:31:50.430Z devp2p:dns:dns got new peer candidate from DNS address=194.33.40.82
2023-10-08T18:31:50.504Z devp2p:dns:dns got new peer candidate from DNS address=159.203.110.190
2023-10-08T18:31:50.594Z devp2p:dns:dns got new peer candidate from DNS address=194.33.40.151

...

[10-08|11:31:55] WARN Engine RPC endpoint not activated on a post-Merge HF setup.
[10-08|11:31:55] INFO ---------------------------
[10-08|11:31:55] INFO Client started successfully
[10-08|11:31:55] INFO ---------------------------

Can check by running DEBUG=devp2p:dns:* npm run client:start -- --discDns --network "holesky"

[acolytec3]

Shippit.

[holgerd77]

@scorbajio cool, thanks for testing! 🤗