Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 634
    • Issues 634
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 116
    • Merge Requests 116
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #2250

Closed
Open
Created Nov 06, 2020 by Arsen Stasic@stasic

DNS Flag Day 2020 - EDNS buffer size configuring does not work anymore

Summary

I think !4179 (merged) introduced a bug, that any config option of max-udp-size or edns-udp-size are not working anymore.

BIND version used

9.16.8 9.11.24

old versions ( 9.16.7 , 9.11.23 ) don't show this behavior

Steps to reproduce

Install new bind and following config:

    edns-udp-size 2000;
    max-udp-size 2000;

But you will still get a TC-bit for queries bigger than 1232 byte.

What is the current bug behavior?

You get the TC-bit even if the answer is lower than 2000 byte long.

What is the expected correct behavior?

Not getting the TC-bit.

Relevant configuration files

    edns-udp-size 2000;
    max-udp-size 2000;

Relevant logs and/or screenshots

With the new version installed on 28th October 2020 the TCP queries for DNSKEY quadrupled: Screenshot_2020-11-06_DSC-Grafana

Possible fixes

I think !4179 (merged) introduced this bug.

Edited Nov 06, 2020 by Arsen Stasic
Assignee
Assign to
December 2020 (9.11.26, 9.11.26-S1, 9.16.10, 9.16.10-S1, 9.17.8)
Milestone
December 2020 (9.11.26, 9.11.26-S1, 9.16.10, 9.16.10-S1, 9.17.8) (Past due)
Assign milestone
Time tracking
None
Due date
None