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 64
    • Issues 64
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • 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
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • dhcp
  • Issues
  • #1

Closed
Open
Opened Mar 13, 2019 by Thomas Markwalder@tmarkMaintainer

Orphan guard records with ddns-dual-stack-mixed-mode enabled

Subtle problem reported by Bluecat via support ticket:

https://support.isc.org/Ticket/Display.html?id=14222

They found a scenario where dual-stack mode does not work correctly. When both ddns-guard-id-must-match and ddns-other-guard-is-dynamic are enabled, the server does not correctly distinguish between no guard record present and guard record present but does not match the client, when a guard record of the other type is present.

This causes the server to decide a v4 A record with a TXT guard record for a different client, is actually a static entry because the same hostname has a v6 DHCID record. It then precedes to replace the A/PTR records and adds another v4 TXT record for the new client.

What it should have done is recognized the presence of a none-matchingTXT record, and not do the updates.

I created a patch (attached) for them that corrects this be adding the necessaryDNS pre-requisite when both of those knobs are true:

14222_v441.patch

Assignee
Assign to
4.4.2
Milestone
4.4.2
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/dhcp#1