How to Enable IPv6 for a Website in Plesk

To make a Plesk website reachable over IPv6, add a shared IPv6 address to its subscription alongside the existing IPv4 address, for example with plesk bin subscription --update example.com -ip 192.0.2.10,2001:db8:100::20. Plesk then generates AAAA records from the DNS template, including for mail and webmail, so check those before you save. A shared IPv6 address can serve websites belonging to many different accounts: you do not need a separate address for each site.

Having an IPv6 address in Plesk’s server list does not by itself make any website available over IPv6. The address must be available to the subscription’s owner, assigned to the subscription, served by working web services and published in DNS.

This guide is for administrators and resellers on Plesk for Linux with root SSH access or administrator access to the panel. If your website is on Noiz shared hosting, IPv6 is available on the shared servers: contact Noiz support to request an IPv6 address for your subscription.

Last reviewed: 13 October 2026, against the current Plesk Obsidian release. This guide is written for Noiz hosting and is kept current against Plesk. It complements, and does not replace, the official Plesk documentation linked below.

Official Documentation Reference

• Plesk: IP Addresses Management: shared and dedicated addresses, and where to register them.
• Plesk: How to change the IP address for a domain or all domains: changing a subscription’s addresses in the panel or on the command line.
• Plesk: How to add an IPv6 address for all subscriptions that have a specific IPv4: rolling IPv6 out in bulk, including reseller IP pools.
• Plesk CLI: subscription: the -ip and -mail-service-ip options.
• Plesk: DNS Settings and template placeholders: what <ipv6> and its variants resolve to.
• curl manual: the --resolve, --ipv4 and --ipv6 options used in the checks below.

Prerequisites

• The server already has a working IPv6 address. If it needs changing first, see How to Change a Plesk Server’s IPv6 Address.
• A backup of the subscription’s hosting settings and DNS zone, and a note of its current IPv4 web and mail addresses.
• A baseline test of the website, webmail and mail hostnames over IPv4, so that any later fault can be compared with how things worked before.

Examples use example.com, IPv4 192.0.2.10 and IPv6 2001:db8:100::20. Replace them with your own values.

Steps at a Glance

1. Confirm the IPv6 address is registered in Plesk as Shared under Tools & Settings > IP Addresses.
2. If the subscription belongs to a reseller, add the address to that reseller’s IP pool. An address available to administrator-owned subscriptions is not automatically available to a reseller.
3. Check the DNS template’s AAAA records and decide whether mail should get one.
4. Assign IPv4 plus IPv6 to the subscription.
5. Test the website directly on the new address, then through DNS.

Plesk assigns addresses per subscription (one IPv4 and one IPv6), so every domain, subdomain and alias in the subscription is affected. List them all before you start.

Check DNS Before You Save

Plesk can generate and publish the new AAAA records as soon as you save the assignment, including to secondary nameservers and any external DNS provider synchronised from Plesk. Check first:

1. Find out where each public record for the domain is actually managed: Plesk, the registrar or an external DNS provider. If the zone is managed elsewhere, add the AAAA records there yourself. Do not switch on synchronisation of an old local copy of the zone just to make an AAAA record appear.
2. Look at the AAAA records in the DNS template. They typically cover the domain itself, ipv6, mail and webmail, plus any names that are CNAME aliases of these.
3. If saving would publish a record for a service that is not ready (usually mail), resolve that before you save. Removing a record afterwards does not help visitors whose resolvers have already cached it.
4. Note the TTL that new AAAA records will get, and the SOA minimum value, which sets how long resolvers remember that a name had no AAAA record. Plesk’s default TTL is 24 hours.

Keeping Mail on IPv4 Does Not Keep Mail DNS on IPv4

The template placeholders <ipv6>, <ipv6.web>, <ipv6.mail> and <ipv6.webmail> all resolve to the same thing: the subscription’s IPv6 address. Assigning mail to an IPv4 address does not stop a mail AAAA record being generated from the template. Check the generated records for the domain, mail, webmail and any aliases separately.

Mail clients that connect to mail.example.com will see a certificate warning unless that domain has its own certificate selected for mail. Check this over IPv4 before you publish any mail record over IPv6, so that an existing certificate problem is not mistaken for an IPv6 fault. Plesk describes per-domain mail certificates in How to assign an SSL certificate per domain to secure the mail server.

Before enabling mail over IPv6, also check the server’s outgoing mail address, its PTR (reverse DNS) record and the domain’s SPF record, then send and receive a real test message.

Assign IPv6 While Keeping IPv4

In the panel, follow Plesk’s subscription IP procedure. On the command line, this example adds IPv6 for web hosting while keeping the original IPv4 for both web and mail:

plesk bin subscription --update example.com \
  -ip 192.0.2.10,2001:db8:100::20 \
  -mail-service-ip 192.0.2.10

Set -mail-service-ip explicitly to the subscription’s current mail address, so that mail stays where it is. If the subscription’s mail used a different address before, use that one. Afterwards, check the subscription’s addresses in the panel and the DNS records Plesk generated.

Test the Website

1. From another network with working IPv6, test the real hostname on the new address:

   curl --noproxy '*' --connect-timeout 10 --max-time 30 \
     --resolve 'example.com:443:[2001:db8:100::20]' \
     --silent --show-error --dump-header - https://example.com/

2. Check the certificate, the page content and any redirect. Test www and every other affected name individually. A server default page or default certificate is a failure even if it returns HTTP 200. Do not add --insecure.

3. Once the records are live, repeat the request without --resolve, adding --ipv6 so that curl cannot fall back to IPv4. Repeat with --ipv4.

4. Test a login or other real page of the application, not just the home page.

5. Query each authoritative nameserver for the domain’s A, AAAA and SOA records, for example dig AAAA example.com @ns1.example.net +short, then check a public resolver. See how to find the IP address of a website or domain for more on lookups. All nameservers agreeing shows the records are published; it does not mean every resolver’s cache has caught up.

6. If the site sits behind a CDN or proxy, test the server directly (with --resolve) and through the CDN separately, and make sure the server’s firewall treats IPv6 the same way it treats IPv4.

How to Remove IPv6 Again

Removing the IPv6 assignment immediately can cut off visitors whose resolvers still hold the AAAA records. Withdraw it in this order:

1. Remove only the new AAAA records, wherever they are managed.
2. Confirm that every authoritative nameserver has dropped them.
3. Keep the website working on IPv6 for at least one full TTL of those records (24 hours with Plesk’s default). Lowering the TTL now does not shorten copies already cached, and some resolvers serve stale answers during DNS failures, so allow some margin.
4. Restore the subscription’s original address assignment (its IPv4 address alone), using the same panel screen or plesk bin subscription --update option you used to add IPv6, then check in the panel that the subscription no longer lists the IPv6 address.
5. Re-test the website, webmail and mail over IPv4, and restore any mail or DNS settings you changed.

If the site is already broken over IPv6, choose whichever supported option restores access fastest. Do not restore the whole Plesk database to reverse one subscription: it would undo unrelated work on the server.

Rolling IPv6 Out to More Websites

Test one website fully (web, webmail and, if in scope, mail) before doing more. Treat mail as a separate step, because a working website over IPv6 says nothing about mail delivery. If you need to change the DNS template during a rollout, read How to Apply Plesk DNS Template Changes Safely first.

Need a Hand?

Noiz manages Plesk hosting and servers for its clients. If your server is on a Noiz managed plan, contact Noiz support with the domains and services involved.