8000 bug: resolver.cloudflare-eth.com is down; change default ENS resolver? · Issue #771 · ipfs/boxo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
bug: resolver.cloudflare-eth.com is down; change default ENS resolver? #771
Closed
@lidel

Description

@lidel

Problem

DNSLinks that use ENS (websites on .eth TLD) are broken for users that run boxo/gateway with default settings (incl. Kubo, Rainbow, IPFS Desktop).

Cloudflare resolver at https://resolver.cloudflare-eth.com/dns-query is currently broken and results no DNSLink results ("Answer":[] at the end):

$ curl -s -H "accept: application/dns-json" "https://resolver.cloudflare-eth.com/dns-query?name=_dnslink.vitalik.eth&type=TXT"
{"AD":true,"CD":false,"RA":true,"RD":true,"TC":false,"Status":3,"Question":[{"name":"_dnslink.vitalik.eth.","type":16}],"Answer":[]

We've reported outage to Cloudflare, but if it does not get fixed until January when the team is back from holidays, we should consider removing .eth support from implicit defaults in Boxo (and Kubo), or switch implicit default to a different DoH resolver.

Solution

We could make things more robust by supporting fallbacks (ipfs/kubo#8173) but for that we need more than one, and it seems ENS has only one stable resolver atm.

So the options are:

Solution (A): do nothing, wait for resolver.cloudflare-eth.com to be fixed

This happens once a year on average. Acceptable? 🤷

Solution (B): remove default resolver for .eth

This would break all ENS websites, and require all end users to choose or set up their own resolver.
Probably not what we want given ENS+IPFS use in the wider ecosystem, but writing this down here for completeness.

Solution (C): switch URL to https://dns.eth.limo/dns-query

The DoH at https://dns.eth.limo/dns-query is a good candidate, seems to be well maintained and provided non-empty DNSLink in "Answer":

$ curl -s -H "accept: application/dns-json" "https://dns.eth.limo/dns-query?name=_dnslink.vitalik.eth&type=TXT"
{"Status":"0","TC":false,"Question":[{"name":"_dnslink.vitalik.eth","type":16}],"Answer":[{"name":"_dnslink.vitalik.eth","data":"dnslink=/ipfs/bafybeifvusbh4iunpvwjlowu47sxnt4hjlebx46kxi4yz5zdsoecfpkkei","type":16,"ttl":300}]}

(this is not final decision, consider this commit as a way fo kicking-off conversation what we should do in 2025 to minimize issues with proxied naming systems like ENS)

Solution (D): ?

Other ideas welcome.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugA bug in existing code (including security flaws)need/triageNeeds initial labeling and prioritization

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0