How to set up your NS servers on VPS?

Question

Domain Name System

Given:
- VPS on Ubuntu 16 + Apache + PHP + MySQL, purchased, let's say superpupervps.ru
- ISPConfig panel installed
- ONE IP address, let's say 10.10.10.10
- Domain, let 's say superpuperdomen.ru , bought from a registrar, let 's say superpuperreg. ru , I can only change the NS-server of the domain, I cannot change any A-records.
Task: I want to provide hosting and reselling hosting services. So that my clients do not know that my site is related to superpupervps.ru
Solution:
Problem #1. I need to bind my superpuperdomen.ru domain to the IP address 10.10.10.10 . This service is provided by the host.superpupervps.ru , you need to register their ns-servers, so it will immediately be clear who I use VPS for. Therefore, you must either use third-party DNS, for example, Yandex. Or raise your DNS, but any registrar requires TWO ns-servers, and I only have ONE IP address. I found this good advice:

The best, in terms of reliability, option for creating and using DNS servers for a VPS / VDS server will be the option when all DNS servers will be on different hardware, that is, on two or four different DNS servers. For example,
you do DNS 1 on your domain and on the main IP address that you will be given when buying a server;
DNS 2 secondary dns you do on a third-party server so that it works when your DNS server crashes;

Problem number 2. How to configure ISPConfig so that I have two NS servers ns1.superpuperdomen.ru and ns2.superpuperdomen.ru ? In order for new sites added via ISPConfig to work (with these NS servers pre-registered). Here's how I wrote:

But then I added a new site to ISPConfig superpupersite.ru and checked:

nslookup
server 10.10.10.10
superpupersite.ru
*** [10.10.10.10] не удалось найти superpupersite.ru: No response from server

Answer 1

you need to register their ns-servers, so it will immediately be clear who I use VPS for.

By the IP address itself, you can easily find out which provider it belongs to. So changing NS servers without changing the IP itself will not add any security. And if you want through some cloudflare or other DDoS protection, then they probably have their own NS server service (cloudflare definitely has it)

Answer 2

SagePtr wrote correctly - it doesn't matter where your dns is, as long as the A-record points to your supervps. So you need to not only mask dns, but also A-record.
In the case of dns, some yandex dns, or something like that will save you.
In the case of hiding hosting, a cheap vps that everyone can see, and from it already forward requests to where you need by installing some haproxy, nginx or something else to your taste