Skip to content

GitLab

  • Menu
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 530
    • Issues 530
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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 Projects
  • BINDBIND
  • Issues
  • #384
Closed
Open
Created Jul 04, 2018 by Michał Kępień@michalOwner

Rework IDN support in dig

IDN support in dig currently suffers from a number of issues:

  • IDNA2003 fallbacks are still present, despite our test comments claiming that BIND made a hard transition to IDNA2008 non-transitional processing,
  • confusing (passing flags which are ignored by the callee) and fragile (locale-dependent) libidn2 calls are used when decoding Punycode found in upstream DNS responses,
  • leftover Autoconf macros from previous IDN implementations are still present,
  • redundant code is present.
Assignee
Assign to
Time tracking