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 572
    • Issues 572
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 110
    • Merge requests 110
  • 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
  • #383
Closed
Open
Issue created Jul 04, 2018 by Petr Menšík@pemensikContributor

delv cannot parse link-local ipv6 addresses with interface number

Summary

delv cannot parse link-local ipv6 addresses with interface number

Steps to reproduce

  • Fedora rawhide container via systemd-nspawn, with ipv6 enabled network provided by libvirt/dnsmasq
  • Use systemd-networkd and systemd-resolved in container
  • networkctl status
●        State: routable
       Address: 192.168.122.82 on host0
                169.254.76.164 on host0
                fc30:XXXX:XXXX:2b0a:3ccb:e4ff:fe52:caa8 on host0
                fe80::3ccb:e4ff:fe52:caa8 on host0
       Gateway: 192.168.122.1 on host0
                fe80::5054:ff:fe2b:eed3 on host0
           DNS: 192.168.122.1
  • /run/systemd/resolve/resolv.conf is linked to /etc/resolv.conf
  • /etc/resolv.conf has autoconfigured content:
  nameserver 192.168.122.1
  nameserver fe80::5054:ff:fe2b:eed3%2

What is the current bug behavior?

delv produces: delv

;; irs_resconf_load: invalid address format
;; resolution failed: not found

What is the expected correct behavior?

Skip address that cannot be parsed or even better parse it correctly

Relevant configuration files

  • /run/systemd/resolve/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 192.168.122.1
nameserver fe80::5054:ff:fe2b:eed3%2

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem.)

Edited Jul 04, 2018 by Petr Menšík
Assignee
Assign to
Time tracking