• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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