• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

9.0.1 DNS issues

Jayson

Basic Pleskian
Any ideas on fixing this?

Domain suspends because of overusuage, I unsuspend however now the domain redirects to a default webpage saying the site is not hosted on the plesk server or hosting is not configured.. Email was also getting bounced saying the host is not in my allowed ctrl file. I restarted email and it works, however the web page still redirects for whatever reason.

This had happened previously with new domains where domain.com works, yet www.domain.com redirected to default Plesk page. Support logged in and ran /usr/local/psa/admin/bin/websrvmng --reconfigure-vhost --vhost-name=domain.com which fixed the problem only until it broke again. When I ran the same command it did not fix the problem, so support again logged and fixed it, allegedly running the same command.

So far since running this upgrade, I have not had one single day without a Plesk problem.... My nice quiet little hosting platform has turned into a monster.
 
I am not sure if this may happen but suspend the domain then unsuspend the domain and see if in
/var/named/run-root/etc/named.conf there is an entry for the domain.

Also do you run your own local dns servers?
 
I have tried suspending and unsuspending with no change. I do have my own nameservers and unfortunately, both are running on the same box.
 
When the domain was suspended did you check /var/named/run-root/etc/named.conf and was the domain removed from there? And when you restored the status in named.conf was the domain put back in?
 
Back
Top