I need a clean, production-ready deployment of Virtualizor on my dedicated server. Everything will be Linux-based, and the end result has to feel like a small private-cloud product that I can start selling straight away. Scope • Create three ready-to-sell VPS plans inside Virtualizor, each with its own resource limits and pricing labels. • Activate internal IP addressing so all guests can communicate over a private network while keeping their public interfaces separate. • Integrate PowerDNS and configure reverse DNS records so every new VPS receives valid PTR entries automatically. • Ensure NoVNC consoles open flawlessly in the client panel, with clipboard support and no mixed-content warnings. • Implement advanced firewall rules: custom port mappings, IP-based restrictions, brute-force mitigation, and any best-practice hardening for the host and the guests. • Apply my logo and a matching color scheme throughout the Virtualizor client and admin portals to give a consistent, branded look. Acceptance checklist 1. Spin-up of each plan succeeds without errors and the VM boots into the selected Linux template. 2. Internal ping between two new VMs works while external traffic follows the public interface. 3. Reverse DNS lookup for a freshly created VPS resolves to the assigned hostname. 4. NoVNC launches from Virtualizor with full keyboard support and stays connected for at least 10 minutes under load. 5. Firewall tests show only the intended ports open externally and rule sets survive a server reboot. 6. Branding displays correctly on the login screen, dashboard, and email notifications. If you have recent experience with Virtualizor, PowerDNS, iptables/firewalld, and front-end tweaks, I’m ready to get started right away.