Status Update
Comments
se...@google.com <se...@google.com> #2
Thank you for sharing this feedback with us.
I have marked this issue as a Feature Request as I understand that this isn’t a Bug, as it’s how currently the UI work.
However, I have forwarded your request to the Cloud DNS engineering team, in order to evaluate the implementation of this change.
If you would like to add any information, or use case, to this issue, please do so in this thread.
Further communications will be made here as well, however I cannot promise an ETA for the resolution of this request.
go...@gmail.com <go...@gmail.com> #3
As far as I can see this issue has already wasted many minutes and hours of Googles paying customers valued time.
go...@cheeri.ai <go...@cheeri.ai> #4
As far as I can see this issue has already wasted many minutes and hours of Googles paying customers valued time.
sd...@gmail.com <sd...@gmail.com> #5
This is such an obvious problem that should have been fixed by now. Seriously, what is the hold up? There are hundreds of articles and DKIM splitting utilities to work around this, it is the highest voted issue tagged with 'google-cloud-dns' on stackoverflow.com the but it's very annoying and for a layperson it's highly confusing. It can't be that hard to fix this. Grab one of your highly paid devs, sit them in front of a computer, and have them knock it out.
WHY ARE YOU IGNORING THIS?
do...@google.com <do...@google.com>
le...@mailhardener.com <le...@mailhardener.com> #6
For GC customers having difficulties with entering longer TXT records in Cloud DNS, we have been offering a Cloud DNS compatible record splitter here:
This is especially useful for DKIM records, which always exceed the maximum length of an RFC1035 <character-string> object.
Description
We (
We would like to propose changing the UI to accept arbitrary strings 'as is' without requiring quoting and retaining whitespace by default.