Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Knot DNS
Knot DNS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 18
    • Merge Requests 18
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Knot projects
  • Knot DNSKnot DNS
  • Issues
  • #468

Closed
Open
Opened Jun 18, 2016 by Daisuke Higashi@hdais

TCP maximum segment size (MSS) option

Please add an option to specify TCP maximum segment size (MSS) for listening TCP socket.

It is known that in some circumstance PMTUD doesn't work correctly, for example under anycast deployment or ECMP server load-balancing [RFC7690]. [RFC7690] suggests to deploy an proxy which receives ICMP Toobig and broadcasts it to all nodes but I think that just setting small TCP MSS for avoiding PMTUD is easier and suitable for DNS.

I submitted similar patch to NSD/Unbound and has been accepted. https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=731 https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=732

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: knot/knot-dns#468