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 566
    • Issues 566
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 94
    • Merge requests 94
  • 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
  • #1178
Closed
Open
Issue created Aug 02, 2019 by reedjc@reedjc

udpsize anomalies

I was trying to understand dig +bufsize. (Reading today's master code.)

  1. The dig manual says bufsize is rounded up to 0 if below.
    See dighost.c's setup_lookup(). It has some code that if udpsize is 0, sets it to 4096. That appears to be the behavior but I didn't trace or debug it. I may have misunderstood the manual. When I set to 0 its behaviour is as if it is at least 2481 (I assume 4096).
  2. dighost.c add_opt() uses the dns_message_buildopt(). See lib/dns/message.c dns_message_buildopt() which has: /* * Set Maximum UDP buffer size. */ rdatalist->rdclass = udpsize; Am I reading this right? how can "rdclass" and udpsize be related? (If this correct, please add documentation.)
  3. Also see lib/ns/client.c process_opt() has: /* * Set the client's UDP buffer size. */ client->udpsize = opt->rdclass; I am trying to understand that udpsize/rdclass relationship. I think is a bug. See right after updsize gets reset to 512 because of this. Again the dig manual reads that bufsize (udpsize) can be less than 512. But if I set to 1, its behavior is as if is set to 512.
Assignee
Assign to
Time tracking