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

Resolved Error: IP address cannot be removed

JesseF

New Pleskian
I got this error today after removing an ip alias from my NIC. Error: IP address x.x.x.x cannot be removed because it is used by DNS zone of one or more domains.

I only have 3 domains on this box and the IP is not listed in any of their' DNS configs. Just wondering if anyone has any ideas. If I choose "repair" it re-aliases the IP to the NIC. I want to completely remove it from this box.

Thanks in advance,

Jesse :)

OS
CentOS Linux 7.9.2009 (Core)
Product
Plesk Obsidian
Version 18.0.33, last updated on Jan 28, 2021 12:21 PM
 
Igor,

Thanks so much. I fixed it. Ran Diagnose and Repair for the Plesk Database and it didnt solve the problem. I just removed the domain that last had that IP and Voila! I'm sure it was a database inconsistency.

Thanks for everything you do on the Forum Igor. I really appreciate you.

--Jesse :)
 
Back
Top