BugFix - Fix the DNS page to allow non case sensitive cname
It seems there is a bug on the DNS page (DNS made easy addon), when adding a cname, it seems to error out with error, when discussing with support it seems to be requiring lower case, 75% sure it's a bug parsing the cname correctly. "Target for CNAME record is invalid", is the error - The context was adding a DKIM record from office365 and some of the letters in the DKIM record were capitalized.
https://learn.microsoft.com/en-us/defender-office-365/email-authentication-dkim-configure
ITRadix
shared this idea
-
Arsal 05 commented
This issue is most likely a validation bug on the DNS page rather than a real DNS limitation, since CNAME targets are inherently case-insensitive. The error (“Target for CNAME record is invalid”) is probably caused by the system enforcing a lowercase-only pattern when parsing the input, which conflicts with DKIM records from services like Microsoft 365 that may include uppercase characters. As a quick workaround, you can simply convert the entire CNAME target to lowercase before submitting it, which will work correctly in DNS. For a proper fix, the validation logic should be updated to accept both uppercase and lowercase characters or normalize the input to lowercase before validation, ensuring compliance with standard DNS behavior. https://tekken3apkzone.com/
-
Alex Alex commented
Overall, the impact of technology https://orinocowind.com on modern society is profound and multifaceted.
-
Evgeniya Virgo commented
From essays to full thesis help, AllEssay.org delivers. Writers follow your instructions precisely. Results are formatted and citation-ready. Academic help made personal. https://allessay.org/
-
William Bolen commented
If you're looking for a reliable way to access legal information and track case details, it's essential to use trusted resources. One such tool is https://mo-case.net , which allows users to search for a variety of case-related information