-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Do not require network i/o for *.libp2p.direct domain resolution #11136
Copy link
Copy link
Closed
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantiteration/2026-q1On maintainer radar for Q1 2026On maintainer radar for Q1 2026kind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featuretopic/dnstopic/libp2pTopic libp2pTopic libp2p
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upeffort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantiteration/2026-q1On maintainer radar for Q1 2026On maintainer radar for Q1 2026kind/enhancementA net-new feature or improvement to an existing featureA net-new feature or improvement to an existing featuretopic/dnstopic/libp2pTopic libp2pTopic libp2p
Checklist
Description
libp2p.direct subdomains are deterministically resolvable without needing to use the OS resolver.
Note: perhaps there's an alternative way to remove pressure on the OS DNS resolver by getting go-libp2p to prefer dialing addresses that don't require DNS resolution until later, but that is likely both more complex and requires getting the changes into go-libp2p. This approach can just use the custom resolver code we already have in place that allows for handling specific domains (e.g. custom resolution for .eth domains).