• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Wrong TXT record implementation in Plesk DNS

ondrejvaroscak

New Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
Plesk Obsidian v18.0.65_build1800241025.12
DNS TXT contains quotes by definition. Example [example.com. IN TXT "This domain name is reserved for use in documentation"]

DNS in Plex doesn't accept quotes in input field, which would be ok, if they would be appended in the zone, but it is not the case. By export to Cloudflare the records are exported without quotes. Cloudflare servers detect and correct this automatically and add quotes to the TXT records.

By Import Cloudflare servers send complete records including quotes, which causes Cloudflare DNS extension to ignore these records and throw error TXT: [Incorrect DNS Record parameter values were specified: ('displayVal' = '"This domain name is reserved for use in documentation;"')]

I believe this is due to:

1. wrong implementation of Plesk DNS interface not following TXT record definition
2. wrong implementation of Cloudflare DNS extension not providing the quoted - nonquoted conversion
 
Hello, @ondrejvaroscak. Thank you for your report. That issue has been brought to our attention and the behavior is identified as a bug with ID EXTPLESK-5352. We will introduce a fix for it in one of the feature releases. You may monitor our change log here. Unfortunately, at this point, we cannot provide a workaround apart from adding the DNS records manually.
 
Hello, @ondrejvaroscak. Thank you for your report. That issue has been brought to our attention and the behavior is identified as a bug with ID EXTPLESK-5352. We will introduce a fix for it in one of the feature releases. You may monitor our change log here. Unfortunately, at this point, we cannot provide a workaround apart from adding the DNS records manually.

There is no problem of managing DNS manually, I do it anyway because Cloudflare DNS extension also doesn't support TLSA records. I was unaware of the Bug as there is no procedure of submitting / reviewing bugs mentioned anywhere on your support / help site.
 
Back
Top