TXT DNS records over 255 characters on Tsohost

Discussion in 'IT & Internet' started by triatic, Sep 10, 2019.

  1. triatic

    triatic UKBF Newcomer Free Member

    3 0
    I am trying to create a DNS record which is over 255 characters long on my Tsohost cPanel account, for the purposes of adding a DKIM key. The problem is, as soon as I go over 255 characters, the system seems to add a space into the TXT record, which breaks the DKIM key.

    Has anyone come across this before?

    Here is a dig result for a random string which is 256 characters long. The system has added a space before the final "y", despite no such space being added into the Zone Editor in cPanel.

    Code:
    C:\>dig txt-test.mydomain.co.uk. txt (at)ns1.tsohost.com
    
    ; <<>> DiG 9.14.4 <<>> txt-test.mydomain.co.uk. txt (at)ns1.tsohost.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9066
    ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    ;; WARNING: recursion requested but not available
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 2800
    ;; QUESTION SECTION:
    ;txt-test.mydomain.co.uk.      IN      TXT
    
    ;; ANSWER SECTION:
    txt-test.mydomain.co.uk. 14400 IN      TXT     "gegopptubufhdeqqhlmndkaqcyabyywrgbxfwfcuzhamiblzpdhoqrhychdwztoelxmgwjbltytrrtethsgujzcpcosllzmwpdvqngmfpsmpemydoxpvkhhtqichiuzmvikkumjrufkpkibgblvkaqdfdopaowyrsqdpnoqehlgkaozcctkgtfxaftgzldtxfzmralfcwmlvcpqciwhabjhyncblawdrljeeysxhogrqkufpmljzbqcefxbnbaj" " y"
    
    ;; Query time: 11 msec
    ;; SERVER: 185.52.27.27#53(185.52.27.27)
    ;; WHEN: Tue Sep 10 14:46:19 GMT Summer Time 2019
    ;; MSG SIZE  rcvd: 324
     
    Posted: Sep 10, 2019 By: triatic Member since: Sep 10, 2019
    #1
  2. Mike Hayes

    Mike Hayes UKBF Enthusiast Free Member

    1,050 271
    Just tried to reproduce this here in cPanel 82.0.14 without an issue (260 chars):

    [​IMG]

    Code:
    ;; ANSWER SECTION:
    
    test.my.domain. 300 IN TXT "5fRkn8TYQDJUfZmik5CZ3fN2RMaGtJ4DMHOapCFcDteHqMXqSgmnzl32ZDP6bRvuzWVvVDZIGYezTCbdKytFLVna1zadiJEYtRvq8pIT702xk03N2lxaKPEJQ3SlY1MJCBi8a1PblifsT0p3ArhxVc1g020T4SeC8jv3LQU62GjTJws2aEnJztlHt9p2zdg6ujphquTtMSoYwPwusa2QJ4dASXPqyiHHvRe1U5Lqqqvg4PxKC3AN8iCe1LITEdU" "YBSpw"
    
    Probably best to contact Tsohost support.
     
    Posted: Sep 10, 2019 By: Mike Hayes Member since: Jan 7, 2016
    #2
  3. triatic

    triatic UKBF Newcomer Free Member

    3 0
    Thanks, I will contact Tsohost support as this issue is almost certainly specific to them. But if there's anyone else using a Tsohost cPanel account reading this it would be great if they could test this too so I know if mine is an isolated case or a wider issue.
     
    Posted: Sep 10, 2019 By: triatic Member since: Sep 10, 2019
    #3
  4. KM-Tiger

    KM-Tiger UKBF Legend Full Member - Verified Business

    9,852 2,619
    What you have is correct.

    The limit of 255 characters comes from DNS where TXT records cannot exceed that length. To split into two quoted parts separated by a space is the workaround and DKIM will reasemble the two parts.

    If your key is not working, there will be some other reason.
     
    Posted: Sep 10, 2019 By: KM-Tiger Member since: Aug 10, 2003
    #4
  5. KM-Tiger

    KM-Tiger UKBF Legend Full Member - Verified Business

    9,852 2,619
    Posted: Sep 10, 2019 By: KM-Tiger Member since: Aug 10, 2003
    #5
  6. Mike Hayes

    Mike Hayes UKBF Enthusiast Free Member

    1,050 271
    There's a space in the actual quoted string (first character of the second string).
     
    Posted: Sep 10, 2019 By: Mike Hayes Member since: Jan 7, 2016
    #6
  7. KM-Tiger

    KM-Tiger UKBF Legend Full Member - Verified Business

    9,852 2,619
    You are quite right, sharper eyes than mine!

    So that must be a bug with Tsohost.
     
    Posted: Sep 10, 2019 By: KM-Tiger Member since: Aug 10, 2003
    #7
  8. fisicx

    fisicx It's Major Clanger! Staff Member

    30,917 9,058
    I thought Tsohost were the bug. Why do people still use these numpties?
     
    Posted: Sep 12, 2019 By: fisicx Member since: Sep 12, 2006
    #8
  9. gpietersz

    gpietersz UKBF Regular Free Member

    169 22
    I find people are very reluctant to switch hosts, even with good reasons to do so.

    I would have thought all the issues Tsohost have had recently would be enough, but they still seem to have a lot of customers.
     
    Posted: Sep 16, 2019 By: gpietersz Member since: Sep 10, 2019
    #9
  10. GURUCLOUD

    GURUCLOUD UKBF Contributor Full Member

    63 3
    TSO are a huge outfit (part of GoDaddy), they merged many different once independent large brands into one single behemoth (TSO) and I'm sure will have many, many happy customers. I think its probably the case that due to their size, they are going to have a few unhappy - who are also generally much more vocal than those happy :)
     
    Posted: Sep 17, 2019 By: GURUCLOUD Member since: Jun 15, 2018
    #10
  11. gpietersz

    gpietersz UKBF Regular Free Member

    169 22
    GoDaddy is not great in my experience. Neither are big shared hosting outfits in general.

    TSO have had a lot of issues recently. I cannot post links yet but search for articles in The Register about their email issues. Failing to fix problems (and it was their fault) that matter to customers is not acceptable.
     
    Posted: Sep 17, 2019 By: gpietersz Member since: Sep 10, 2019
    #11
  12. triatic

    triatic UKBF Newcomer Free Member

    3 0
    The "fix" from Tsohost was to re-generate the DKIM key with 1024 bits instead of 2048 which seems to be cPanel's default. 1024 bit DKIM keys fit inside 255 character txt records.

    Obviously the real fix would be for Tsohost to fix their DNS infrastructure so that txt records function correctly over 255 characters and allow for the longer, more secure DKIM key size.
     
    Posted: Sep 20, 2019 By: triatic Member since: Sep 10, 2019
    #12