Article ID: 115507, created on Feb 8, 2013, last review on May 9, 2014

  • Applies to:
  • Odin Business Automation Standard 4.x
  • Plesk 11.x for Linux
  • Plesk 10.x for Linux


When creating a Forwarding-only hosting package on a Plesk 11 node with both IPv4 and IPv6 IP addresses,  the package is only assigned one IP address type: IPv4 or IPv6 address.
For example, suppose Plesk domain domain.tld uses both IPv4 and IPv6 addresses. When changing domain hosting to Forwarding via API, domain's DNS zone is updated with one IP address type - DNS records  point to IPv4 or IPv6 address only.

Here is DNS zone of domain with IP_ADDRESSv4 and IP_ADDRESSv6 addresses whose hosting type was changed to Forwarding via API:
www.domain.tld. CNAME domain.tld.
ipv6.domain.tld. AAAA IP_ADDRESSv6
ftp.domain.tld. CNAME domain.tld.
mail.domain.tld. AAAA IP_ADDRESSv6
domain.tld. AAAA IP_ADDRESSv6
domain.tld. MX 10 mail.domain.tld.
IP_ADDRESSv6 PTR 64 domain.tld.
domain.tld. NS ns.domain.tld.
webmail.domain.tld. AAAA IP_ADDRESSv6

Where IP_ADDRESSv6 is domain’s IPv6 address. You may see DNS records pointing to IP_ADDRESSv4 address are missing. And vice versa: DNS zone may contain DNS records pointing to IP_ADDRESSv4 only.


When updating hosting preferences of a Plesk domain to forwarding with both IPv4 and IPv6 addresses via API, only one IP address type is added into domain DNS zone: this may be IPv4 or IPv6 address.


The issue will be fixed in a future update of Parallels Plesk Panel that will be released after version 11.1. The hotfix for Parallels Plesk Panel version 11.0.9 is attached.

Install it on the Parallels Plesk Panel 11.0.9 server with the following command:

[root@plesk11.0.9 ~]# tar -zxf plesk11.0.9_hotfix129068.tar.gz -C /
[root@plesk11.0.9 ~]# chown root:root /usr/local/psa/admin/plib/api-rpc/AgentWebSpace.php
[root@plesk11.0.9 ~]# chmod 644 /usr/local/psa/admin/plib/api-rpc/AgentWebSpace.php


70a5401e8b9354cd1d64d0346f2c4a3e caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 dd0611b6086474193d9bf78e2b293040 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF