Troubleshooting Tip: How to fix 'No DKIM record found' when adding a DKIM record for DNS Zone

[tnazarov]

Description	This article describes how to fix the error 'No DKIM record found' when adding a DKIM record for the DNS Zone.
Scope	FortiADC v6.0.0 and later.
Solution	Testing tools for DKIM records will give the error when configuring DKIM records as shown below based on this configuration: show     config txt-record         edit 5             set name TM-DKIM-20240856181212._domainkey.TESTING.com             set text " v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCs4o7hj2e6jhbLfC9JZz5AmYsW5HvIfi+Zo1T8Z9GzZ2uBxeYwN+9cJ+OWa3s/DuJ+Hc1a8NzpZy93bxdE+nM/zZxZlfDFJcH/B5o7Hq4RmXbbrmG15m5I4BO2zLXnZ3/jKo9w5bXs67RhJH2uB9M4eYaL+ks9uJ4D2TrZ5EcsG0a+Fo0bZfQIDAQAB"             set ttl 30     next end When configuring a DKIM record in the ADC Global DNS Zone, it is not necessary to add the domain name at the end of the DKIM record. Instead of configuring 'set name TM-DKIM-20240805181212._domainkey.TESTING.com', the TXT record name on FortiADC should be configured as 'tm-dkim-20240805183219_domainkey'. After adding the DKIM record accordingly, it is possible to see the DKIM record for the site. After adding or modifying a DKIM record, it is important to verify DNS propagation, as changes may take time to reflect across global DNS servers. Tools such as nslookup, dig, or online DNS propagation checkers can be used to ensure the record is active and accessible. Verifying propagation confirms that the DKIM record is correctly configured and resolved, addressing issues related to DKIM records not appearing or functioning as expected. Common issues and fixes regarding DKIM record: DKIM record not appearing in DNS: Verify the record was saved correctly in the DNS management console. Syntax errors in the record: Validate the TXT record syntax and formatting. DKIM records must not contain unexpected line breaks. If the key is too long, use DNS management tools that support record splitting.