Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dhcp
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 18
    • Merge Requests 18
  • 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
  • dhcp
  • Issues
  • #28

Closed
Open
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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None