• 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!
  • 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.

Search results

  1. S

    Issue IPv6 ranges not working as they should

    For example, if you give a Docker daemon v6-fixed-cidr of 2a01:4f9:2b:f810::/64, it will in fact allocate ::1 to itself and all others in order to containers so it's understood as a network prefix, so why's this any different? You are supposed to be able to configure a IPv6 prefix of /64 for...
  2. S

    Issue IPv6 ranges not working as they should

    Then how are you supposed to do that for IPv6? In almost all other instances, outside Plesk that's understood as a prefix as I cannot simply do 2a01:4f9:2b:f810::/64 as it will not accept it, but most other applications does accept it.
  3. S

    Issue IPv6 ranges not working as they should

    Hi, When I add an IPv6 range like 2a01:4f9:2b:f810:0:0:0:1 -> 2a01:4f9:2b:f810:ffff:ffff:ffff:ffff (Mask /64), it will only use the 2a01:4f9:2b:f810::1 address for all of the sites, and not allocate one IP per site from it, why's that? I don't think that's how it's supposed to work?
Back
Top