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 627
    • Issues 627
    • 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
  • #1952

Closed
Open
Created Jun 18, 2020 by Evan Hunt@eachOwner

IPv6 addresses can be unparsable in yaml

IPv6 addresses sometimes end in two trailing colons. For example, in the current output of dig +yaml ns by there's a name server with address "2a05:4800:1:100::". This breaks YAML parsing.

To fix this we need to append "0". I think it would be harmless in all IPv6 address expansions everywhere, but in any case we should always do it when using dns_masterstyle_yaml.

Assignee
Assign to
July 2020 (9.11.21, 9.11.21-S1, 9.16.5, 9.17.3)
Milestone
July 2020 (9.11.21, 9.11.21-S1, 9.16.5, 9.17.3) (Past due)
Assign milestone
Time tracking
None
Due date
None