Just wasted whole day with plesk webhosting :D

Decided to move to a DDOS protected hosting by OVH.com

Chose plesk web hosting

Turns out in order to park domain to plesk webhosting it's necessary to change GLUE records and nameservers to point to plesk VPS IP

My domain registrar where I have 10+ domains does not allow changing GLUE records. Only way to make it work would be to move all domains to new registrar and pay for each domain as it's a new one.

FML just wasted 16 euros on this useless plesk webhosting. Need to take regular webhosting :D

We got a lot of malicious traffic from OVH servers anyways. Seems to be a place were malicious actors gather

@steaksauce Especially SSH brute-forcing bots, yeah.

It's not plesk that needs the glue records but the fact that you want to use Plesk directly as DNS server, without your registrar in between.
If your registrar allows changing NS records, you're good to go, however it's always recommended to use at least two different name servers, some registrars even disallow using the same ip twice.
That being said, create two (or more) A and AAAA records with your registrar, as an example ns1.foobar.com and ns2.foobar.com (obviously point these to the respective server). Now set these as new NS records (often called a NS set), eg ns1 -> ns1.foobar.com and ns2 -> ns2.foobar.com and now your registrar should forward uncached requests to Plesk and renew its cache after the TTL expires.
???
Profit