• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs PLESK BIN DNS fails

tkalfaoglu

Silver Pleskian
TITLE:
PLESK BIN DNS fails​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
OS ‪CentOS Linux 7.6.1810 (Core)‬

Product Plesk Onyx
Version 17.8.11 Update #39, last updated on Feb 9, 2019 03:31 AM

PROBLEM DESCRIPTION:
The following command should work according to its documentation:

plesk bin dns --set abc.com -list "TXT,,v=spf1 mx a ip4:1.2.3.4 ip4:1.2.5.4/29 ?all;"

(domain and IP's modified)
But it returns a:
Domain has no NS DNS record.

exit status 1

error instead. The abc.com does exist, its DNS is enabled and primary.​
STEPS TO REPRODUCE:
Enter the plesk bin dns command to set the SPF from the CLI​
ACTUAL RESULT:
plesk bin dns command returns error​
EXPECTED RESULT:
plesk bin dns command should have updated the TXT record of abc.com​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
dns: DNS Zones on Domains.
According to the documentation, plesk bin dns --set removes all pre-existing resource records from a domain's DNS zone and adds the specified ones, which is not suitable for this usecase.
To update the DNS record, remove it using plesk bin dns --del and then add the new one using plesk bin dns --add.
 
Back
Top