Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 591
    • Issues 591
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #3635
Closed
Open
Issue created Oct 31, 2022 by Jeremy Saklad@Saklad5

Implement support for DNS over QUIC

Description

DNS-over-QUIC, specified in RFC 9250, has considerable advantages over the already-implemented options.

  • With the debatable exception of DoH and HTTP/3, it is the only standardized encrypted DNS protocol to operate over UDP.
  • It avoids issues such as head-of-line blocking and potential for amplification attacks.
  • It avoids the overhead of DNS-over-HTTPS.

Request

DNS-over-QUIC should be offered wherever DNS-over-HTTPS or DNS-over-TLS is, at minimum. Its use should be encouraged over the others where applicable.

RFC 9250 emphasizes the following scopes of usage:

  • the "stub to recursive resolver" scenario (also called the "stub to recursive" scenario in this document)
  • the "recursive resolver to authoritative nameserver" scenario (also called the "recursive to authoritative" scenario in this document), and
  • the "nameserver to nameserver" scenario (mainly used for zone transfers (XFR) RFC1995 RFC5936).

I believe that covers every function of BIND.


While not specific to DNS-over-QUIC, the implementation should be designed with future support for non-standard ports and SVBC records in mind. 53/udp is explicitly banned for use with this protocol, but it should eventually be possible to use any other non-standard port rather than 853/udp.

Edited Oct 31, 2022 by Jeremy Saklad
Assignee
Assign to
Time tracking