• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

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

Paul Hermans

Basic Pleskian
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
 
The problem might be with using wrong API request. IPv4 and IPv6 addresses should be specified in two places:

Code:
<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.
 
Back
Top