Skip to content
This repository has been archived by the owner on Nov 13, 2018. It is now read-only.

CNAMEs do not validate with DNSSEC #811

Closed
elsloo opened this issue Nov 23, 2015 · 0 comments · Fixed by #814
Closed

CNAMEs do not validate with DNSSEC #811

elsloo opened this issue Nov 23, 2015 · 0 comments · Fixed by #814
Assignees
@elsloo
Labels
bug Traffic Router
Milestone
1.4.0

Comments

@elsloo
Copy link
Contributor

elsloo commented Nov 23, 2015

CNAMEs are not validating when DNSSEC is enabled due to the fact that no RRSIGs are in the answer section.
@elsloo elsloo self-assigned this Nov 23, 2015
@elsloo elsloo modified the milestones: 1.3.0, 1.4.0 Nov 23, 2015
elsloo added a commit to elsloo/traffic_control that referenced this issue Nov 23, 2015
@elsloo
Fixes an issue that prevented DNSSEC signatures from being included i…
77ec605 
…n CNAME responses which caused validation to fail. This closes Comcast#811.
@elsloo elsloo mentioned this issue Nov 23, 2015
Merged
elsloo added a commit to elsloo/traffic_control that referenced this issue Dec 1, 2015
@elsloo
Fixes an issue that prevented DNSSEC signatures from being included i…
5e8f43b 
…n CNAME responses which caused validation to fail. This closes Comcast#811.

(cherry picked from commit 77ec605)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@elsloo elsloo

Labels
bug Traffic Router
Projects
None yet
Milestone
1.4.0
Development

Successfully merging a pull request may close this issue.

Fixes an issue that prevented DNSSEC signatures from being included i… elsloo/traffic_control
1 participant
@elsloo