Official Go implementation of the Ethereum protocol

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Lucas 804d45cc2e p2p: DNS resolution for static nodes (#30822) ... Closes #23210 # Context When deploying Geth in Kubernetes with ReplicaSets, we encountered two DNS-related issues affecting node connectivity. First, during startup, Geth tries to resolve DNS names for static nodes too early in the config unmarshaling phase. If peer nodes aren't ready yet (which is common in Kubernetes rolling deployments), this causes an immediate failure: ``` INFO [11-26|10:03:42.816] Starting Geth on Ethereum mainnet... INFO [11-26|10:03:42.817] Bumping default cache on mainnet provided=1024 updated=4096 Fatal: config.toml, line 81: (p2p.Config.StaticNodes) lookup idontexist.geth.node: no such host ``` The second issue comes up when pods get rescheduled to different nodes - their IPs change but peers keep using the initially resolved IP, never updating the DNS mapping. This PR adds proper DNS support for enode:// URLs by deferring resolution to connection time. It also handles DNS failures gracefully instead of failing fatally during startup, making it work better in container environments where IPs are dynamic and peers come and go during rollouts. --------- Co-authored-by: Felix Lange <fjl@twurst.com>		2 months ago
..
idscheme.go	…
idscheme_test.go	…
iter.go	…
iter_test.go	…
localnode.go	…
localnode_test.go	…
node.go	p2p: DNS resolution for static nodes (#30822)	2 months ago
node_test.go	p2p: DNS resolution for static nodes (#30822)	2 months ago
nodedb.go	…
nodedb_test.go	…
urlv4.go	p2p: DNS resolution for static nodes (#30822)	2 months ago
urlv4_test.go	p2p: DNS resolution for static nodes (#30822)	2 months ago