What should we do about Cloudflare's TXT record warnings? #3810
Unanswered
tlimoncelli
asked this question in
Q&A
Replies: 4 comments
|
P.S. I have filed a feature request for Cloudflare to provide encoding/decoding functions so we don't have to keep guessing. cloudflare/cloudflare-go#4205 |
0 replies
|
Your image is broken. |
0 replies
|
I've written a request for such utility functions. cloudflare/cloudflare-go#4205 Please upvote it if you agree. |
0 replies
|
I've used my support contract with Cloudflare to request that this feature request be reviewed. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Issue
The way that DNSControl updates TXT records makes Cloudflare report this warning:
They are just warnings. Cloudflare serves the TXT records exactly as we desire. However people see the warning and file bug reports such as #3621 (comment).
We have 2 options:
What should we do? Option 1 works. Option 2 could introduce new bugs. It is difficult to test.
All reactions