Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 530
    • Issues 530
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 100
    • Merge requests 100
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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 Projects
  • BINDBIND
  • Issues
  • #2992

Closed
Open
Created Nov 01, 2021 by Artem Boldariev@artemOwner

Replace "tcp-only" with a more generic option

Bind has a tcp-only option to force interaction with a server using TCP only.

server <address> {
    ...
    tcp-only yes;
    ...
};

This option was enough when DNS was using UDP and TCP only (Do53), however as it becomes possible to carry DNS traffic with more transports, we might need to replace this option with a more generic one which could specify the desired transport explicitly, e.g.:

server <address> {
    ...
    transport tcp; # or "tls", or "quic" (in the future), etc
    ...
};

When the option is omitted, it means use the default (Do53 - the current behaviour).

This issue, in a way, mirrors #2776 (closed).

Assignee
Assign to
Time tracking