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 576
    • Issues 576
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 111
    • Merge requests 111
  • 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
  • #746
Closed
Open
Issue created Nov 27, 2018 by Ray Bellis@rayDeveloper

static stub zones can't point to IPv6 scoped addresses

It appears to be impossible to configure BIND to point a static stub zone at a scoped address (e.g. fe80::1%eth0).

The error message suggests that the restriction is deliberate, but I can't tell why it's imposed:

/etc/named.conf:44: scoped address is not allowed for static stub server-addresses

Using a scoped address would be desirable when using IPv6 link-local addressing to talk to a private server that doesn't otherwise have a global unicast address on it.

Assignee
Assign to
Time tracking