Skip to content

DNS over TLS #39808

Description

@szmarczak

Is your feature request related to a problem? Please describe.

So third parties can't tamper with DNS.

Describe the solution you'd like

resolver.setServers(['tls://1.1.1.1']); // port defaults to :853

Describe alternatives you've considered

None yet.

Related: https://developers.cloudflare.com/1.1.1.1/dns-over-tls

Activity

  1. added
    dnsIssues and PRs related to the dns subsystem.
    feature requestIssues requesting new Node.js features.
    on Aug 19, 2021
  2. targos commented on Aug 21, 2021

    @targos
    Member

    This can probably only be fixed by switching from c-ares to getdns: #38184

  3. moved this to Pending triage in Node.js feature requestson Jan 16, 2022
  4. github-actions commented on Mar 29, 2022

    @github-actions
    Contributor

    There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

    For more information on how the project manages feature requests, please consult the feature request management document.

  5. added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Mar 29, 2022
  6. moved this from Pending Triage to Stale in Node.js feature requestson Mar 29, 2022
  7. szmarczak commented on Mar 29, 2022

    @szmarczak
    ContributorAuthor

    unstale

  8. bnoordhuis commented on Mar 31, 2022

    @bnoordhuis
    Member

    We never moved away from c-ares and I suspect it's unlikely to grow such functionality anytime soon1 so I'd move to close this as a wontfix (or rather: wonthappen.)

    1 You could open an issue over at https://github.com/c-ares/c-ares/issues inquiring if there's interest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dnsIssues and PRs related to the dns subsystem.feature requestIssues requesting new Node.js features.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions