Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dhcp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 128
    • Issues 128
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • 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
  • dhcp
  • Issues
  • #28
Closed
Open
Issue created Jun 26, 2019 by Cathy Almond@cathyaDeveloper

Update documentation to clarify that FQDNs configured in DHCP (e.g. next-server) are resolved only once, on startup

It is not clear in the ISC DHCP documentation that when an option that will be used operationally as an IP address is configured using a FQDN, that this will be resolved only once and the resulting IP address used thereafter and never refreshed.

In other words, DHCP is doing a one-time resolution of the FQDN that had been configured for convenience instead of using an address. The TTL of the DNS query response is not observed and the FQDN will not be resolved again until the server is restarted.

This might lead to mis-set expectations when designing a deployment that assumes that it is possible (by means of rotating DNS query responses) to load balance some client provisioning. For example: Support ticket 14783

Assignee
Assign to
Time tracking