Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 499
    • Issues 499
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 27
    • Merge Requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • 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
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #6132

Closed
Open
Created Mar 29, 2021 by Jesse Norell@jnorellDeveloper

dns: better cname checks

Need to implement more/better checking for CNAME records to prevent invalid records. Eg. not long ago someone reported an issue which was caused by creating CAA records for a hostname which had a CNAME records. Just now I created a CNAME record for a hostname which already had a TXT record, which is invalid. We should look up the exact set of what is allowed to be present with CNAME and only allow those.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None