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

DNS problems, reseller problems, a lot of problems.

lvalics

Silver Pleskian
Plesk Guru
I was very patient since I have upgraded to PLESK 10.x

Now I lose all my patience and I can say that guys, it is bad.
I never saw in any PLESK release so many errors, bugs, which shouldn't be there.

The most recent one, beside of the lot what is on the forum, DNS and reseller.

I have resellers who maintain around 30 domains.
Each time when someone goes above the limit of the resource, the domain is deactivated and he cannot reactivate normally.

I have found the solution, but is over my mind.

I need to go to the domain control panel, reset the domain DNS (deactivate/reactivate) and then go to command line and reconfigure the domain.

Just simple suspens/activate the domain will not work, only this solution is working.

After my investigation, named.conf does not contain the domain information, nothing help only this solution.
This seems to happening only to resellers, even if they have all rights to do anything.

Anyway, this is now a major one, the rest are small but a lot :-(
 
Hi! thanks for the info. Could you please share with us how to "go to command line and reconfigure the domain"?
Thank you very much
 
Seems not need this command line reconfigure, just need to go to control panel of the domain and deactivate/reactivate the DNS. NASTY BUG :-(
 
Thanks for the reply. I've experienced this situation twice when trying to activate a domain that had been deactivated due to expire date.
 
Back
Top