DKIM authentication

[reseng]

I am trying to get my workspace to authenticate DKIM but despite my best efforts I cannot seem to get it authenticated. I have been stuck at this point for last 3 weeks and it is really taking it's toll on productivity. I generated TXT record using 2048 key length and then added the record in two parts using quotation marks as domain won't allow longer records (google recommendation). I tried 1024 too, which generates shorter record and doesn't need to be added in parts.

I tried using MXtoolbox.com and the TXT record returned is different to what I have in Workspace and on the domain. Google toolbox times out when I try to run checks on my domain. And I can't contact google as google refuses connection when I click feedback. I tried generating new record many times before you make a guess. Cannot understand the disconnect. Any help will be greatly appreciated.

[KAM]

@reseng what service are you using for DNS because you might need to ask them for help creating a record.  For example, some interfaces require you to add two entries with the same name when a record is too long.  If you can do a test lookup and the record comes back like "Test...." "123" than the quotes and the spaces are removed by clients automatically. HTH, KAM

[reseng]

@KAM I also tried using the 1024 key length generated by google workspace but there is a disconnect somewhere. What I see when I use the MXtoolbox.com is totally different from google workspace and domain, quotes or no quotes.

[KAM]

@reseng What DNS provider are you using?  -KAM

[groft]

@reseng Can you share more about "the TXT record returned is different to what I have in Workspace and on the domain"? You can redact your actual domain name and keep everything else the same. 

I'm curious if there's an issue with a terminal dot in your dkim DNS record, which would determine whether your domain name gets appended incorrectly. In other words, the TXT records beginning with:

google._domainkey

google._domainkey.

google._domainkey.sub.domain.com

google._domainkey.sub.domain.com. 

all result in different records.

[groft]

@reseng, Two other things to ask, just to make certain key steps are done:

1. Did you click the Start Authentication button in the DKIM authentication section of Authenticate email settings?

2. Is it possible that your DNS already had a google._domainkey record for your domain (or whatever selector you chose, if not the default "google" as shown here)? You mentioned the TXT record returned is different than expected, so it may be that you're seeing the already-existing record for the selector. Someone could have created one before and bailed on the whole setup, but didn't remove that record from DNS. 

[anhvancodon]

Thật sự là mấy năm nay tôi thường xuyên bị chiếm quyền truy cập và tôi chưa
biết về nhiều vấn đề Nâng cao vì tôi không học Công nghệ, do là yêu mến
Cộng đồng và các Nền tảng nên ngày đêm tìm hiểu thông tin bổ ích về Phổ
biến lại cho người dùng, tôi chưa từng mua miền. Tôi chỉ có tài khoản
G-Suite. Tôi định sang năm mới cải thiện lại tất cả và học hỏi thêm
nhiều...!
Cảm ơn bạn và chúc Sức khỏe 💗
*Nếu có vấn đề gì cứ mail cho tôi và có thông tin bổ ích xin được học hỏi...
Chào. 💗

null.