• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Forwarded to devs XML-RPC doesn't return TTL for DNS records

Kaspar

API expert
Plesk Guru
Username:

TITLE

XML-RPC doesn't return TTL for DNS records

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk version 18.0.39

PROBLEM DESCRIPTION

Plesk supports modifying TTL values for individual since version 18.0.31, however but this isn't available for the XML-API yet. This isn't a bug (obviously), but rather a lacking feature of core functionally in the XML-API (imho). Since the REST API doesn't seem to support adding DNS records to a domain (yet), it would be useful to have TTL supported in the RCP-XML api.

STEPS TO REPRODUCE

Body for XML-RCP API
XML:
<packet><dns><get_rec><filter><dns-zone-name>example.com</dns-zone-name></filter></get_rec></dns></packet>

ACTUAL RESULT

XML Response
XML:
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.9.1">
    <dns>
        <get_rec>
            <result>
                <status>ok</status>
                <id>1</id>
                <data>
                    <site-id>302</site-id>
                    <type>CNAME</type>
                    <host>www.example.com.</host>
                    <value>example.com.</value>
                    <opt></opt>
                </data>
            </result>
        </get_rec>
    </dns>
</packet>

EXPECTED RESULT

XML Response
XML:
<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.6.9.1">
    <dns>
        <get_rec>
            <result>
                <status>ok</status>
                <id>1</id>
                <data>
                    <site-id>302</site-id>
                    <type>CNAME</type>
                    <host>www.example.com.</host>
                    <value>example.com.</value>
                    <ttl>1800</ttl>
                    <opt></opt>
                </data>
            </result>
        </get_rec>
    </dns>
</packet>

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
"It is now possible to add and manage DNS records (including TTL) in a DNS zone via REST API.": https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18036
Thats unfortunate, because the REST API doesn't seem to support adding DNS records. Even tough the change log for Plesk 18.0.36 mentions the option to add DNS records via the REST API the methode actually isn't available. Only methodes for retrieving (GET) or updating (PUT) DNS records are actually available for the REST API.

Schermafbeelding 2021-11-24 om 10.06.00.png

Which means there is no option to add DNS records to Plesk with TTL values with either the REST API or the XML-RCP API.

Or am I perhaps missing something?
 
Last edited:
@Rasp, you are correct. Internal task PPP-55178 ("Allow adding/removing DNS records via REST API") is created.
 
Back
Top