Forwarded to devs Plesk API bug: IPv6 DNS records not added

[Paul Hermans]

TITLE:

Plesk API bug: IPv6 DNS records not added​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Windows Server 2016 and Plesk Onyx 17.8.11​

PROBLEM DESCRIPTION:

When we create a new subscription in Plesk via the API, the IPv6 DNS records are not added to the domains DNS-zone. The IPv6 address is available under "Web Hosting Access" but the records are missing. When you click on DNS Settings > "Reset to default" the IPv6 records show up.​

STEPS TO REPRODUCE:

Create a new subscription in Plesk via the API with IPv4 and IPv6.
Click on DNS Settings and see IPv6 records are missing​

ACTUAL RESULT:

Click on DNS Settings and see IPv6 records are missing​

EXPECTED RESULT:

DNS Settings > IPv6 records expected from DNS template​

ANY ADDITIONAL INFORMATION:

This problem does not exist on Plesk for Linux, only on Plesk for Windows. I had contact with Hostfact and the API calls are the same for Windows and Linux.​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

The problem might be with using wrong API request. IPv4 and IPv6 addresses should be specified in two places:

<packet>
  <webspace>
    <add>
      <gen_setup>
        <name>example.com</name>
        <ip_address>1.1.1.1</ip_address>                     <------------------------------------
        <ip_address>2001:0db8:85a3:0000:0000:8a2e:0370:7334</ip_address>   <------------------------------------
      </gen_setup>
      <hosting>
        <vrt_hst>
          <property>
            <name>ftp_login</name>
            <value>login</value>
          </property>
          <property>
            <name>ftp_password</name>
            <value>passwd</value>
          </property>
          <ip_address>1.1.1.1</ip_address>                     <------------------------------------
          <ip_address>2001:0db8:85a3:0000:0000:8a2e:0370:7334</ip_address>   <------------------------------------
        </vrt_hst>
      </hosting>
    </add>
  </webspace>
</packet>

Specifying only IPv4 address in *gen_setup* node leads to the behaviour that you faces.
Though omitting IPv4 address works for unix it is not recommended to do this because it might lead to inconsistencies.