How to transfer your ns servers to amazon r53?

Question

Domain Name System

Good day!
The situation is as follows - it is necessary to delegate various domains from any registrars to their own ns-servers.
There is an example.com domain which is delegated to Amazon's R53 (the ns-servers that Amazon issued when creating the hosted zone are specified in the domain settings).
Also in the hosted_zone there are a number of records like
ns1.example.com
ns2.example.com
....
nsN.example.com
each of which points to a DNS server from Amazon (either through CNAME or A-record to a specific ip- address) ns1.example.com ns2.example.com .... and not those that Amazon gives when creating a host zone I tried to do this:
The question is:
is it possible to transfer, for example, the domain.com domain to the Amazonian R53 (having previously created the corresponding hosted zones in the R53 panel) by specifying the delegated ns-servers in the registrar panel:
1. for the domain.com domain, I registered ns1.example.com, ns2.example.com ...
2. Created a hosted zone with the name domain.com in the R53 panel
3. Added the values ​​of ns-servers to the list of ns1.example issued by Amazon. com, ns2.example.com in the R53 panel
4. In the SOA record, I left the authoritative server issued by Amazon for this host zone
5. Added an A-record for the domain pointing to a server in the data center.
As a result, host resolving does not work, although the information about ns-servers in the whois domain is correct and even the subnet of the data center and its name are determined, into which the A-record looks domain.com domain.
I can’t understand which authoritative zone server should be registered in SOA for such a scheme - Amazon’s or my own (nsN.example.com)
The task is to transfer client domains to R53, while issuing their own ns-server records, not Amazon
’s so I do in this scheme ... or in general everything is wrong :)

Answer 1

The task is initially stupid and has no solution. Since the Amazon ns are not tied to the IP in any way, that is, today the Amazon NS has one IP and tomorrow another.