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 577
    • Issues 577
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 116
    • Merge requests 116
  • 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
  • #1734
Closed
Open
Issue created Apr 03, 2020 by Peter Davies@peterdDeveloper

edns behaviour on forward only configuration

Description

I would like is a way to fix the advertised payload and guarantee it will always stayed fixed because I know my environment and I don't need BIND to try and work out what the forwarders or the intervening will permit.

  1. Use existing settings to infer how EDNS payload advertisement should work. e.g. if 'forward only' is enabled, don't do slow start. The danger with this is there might be a use case that needs both. or
  2. A new configuration parameter e.g. 'edns-udp-behaviour' that takes arguments "fixed" or "auto"

see RT #16201

Assignee
Assign to
Time tracking