-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate absolute DNS name requirement on StaticDNS CNAME #4743
Comments
So is the preferred solution to make it so that a CNAME can be added without a trailing . or so that such CNAMEs would be rejected by the API? |
Yes. Implementer's choice. |
Or at least update the documentation with a CNAME example showing it's a requirement |
Triaging silent errors, reading stack traces, and digging through 3rd party library source code to find out what "Absolute" means is not something operators can afford to be doing during an outage. |
when you create a federation cname, you have to add the trailing dot. i say we keep it consistent and just require the trailing dot. |
this is the error you get if you leave out the trailing dot.
|
also, i added the |
I also changed the title @jhg03a - hope you don't mind. |
That's fine. It just needs a helpful message to go with and not just "denied" |
I put the |
@jhg03a : Does the trailing period affect only DNS type cname_record or the other 3 as well? |
CNAME is where I found it. In theory it would be anywhere we specify the Dns name of a record that uses that library to validate. |
fixed per #4934 |
I'm submitting a ...
Traffic Control components affected ...
Current behavior:
When I was creating a Static DNS CNAME record, I added
domain.foo.com
to a new DS and snapshotted.This causes the snapshot to fail to apply with no user feedback except to go dig around in TR logs.
Expected / new behavior:
Please remove the footgun of forgetting the trailing dot in the CNAME address and better safeties to prevent it from becoming part of a snapshot.
Minimal reproduction of the problem with instructions:
Anything else:
The text was updated successfully, but these errors were encountered: