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
  • #656

Closed
Open
Opened Sep 27, 2019 by Anand Buddhdev@anandb

Compression of names in RDATA

I've just noticed that Knot 2.8.4 doesn't compress names in the RDATA of a response. Mostly this is not a problem. However, there is one special query, where this behaviour results in a sub-optimal response. This is the priming query against a root name server (without EDNS). Whereas BIND and NSD both return a priming response containing 15 glue records, Knot only returns 4 glue records, because it has no more space left for the others. This does not break anything, but a resolver has to issue several follow-up queries to obtain the remaining A and AAAA records of the root name servers.

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