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

dns problems

  1. AYamshanov

    Instruction How to start with Slave DNS Manager 1.0

    Intro This article is short step-by-step how-to about configuring slave DNS server based on CentOS7 and managed by "Slave DNS Manager" on Plesk. I already created a virtual server based on CentOS7 in a cloud environment. The server has public IP-address on eth0 interface. In other words, the...
  2. steveb

    Question TXT and SOA DNS records not propagating

    4 days ago I decided to start using PLESK's DNS server as the primary name server for my DNS Zone and domain climatestore.com. I added new TXT records, to support integration with a bulk Email provider, to the the zone and 'updated' them. I then tested if they were 'visible' using the 'dig'...
  3. M

    DNS problem when ctraet a subdomain

    hi after upgrading plesk from 11.x to 12.x , when i must creat a subdomain, shows the "Error: DNS record already exists." after this error, the A record of subdomain was maked but the directory not!!! this error is for all subdomain names. the subdomains that i was created before upgrading the...
  4. I

    After automated update - Config files corrupted and rebuild breaks all dns on server all sites down

    Im currently hosting a vps server with OVH. after an automated update this last weekend, all my sites went down. OVH told me that the httpd.conf file was improperly updated to port 7080 instead of 80. So I fixed that and then a cascade of errors followed. all the config files somehow were...
Back
Top