I have a domain that is something like mydomain.com and I want to manage the DNS for it myself using my own DNS servers (on a completely different domain - EDIT): ns1.myowndns.com, ns2.myowndns.com, etc... When I try to update the nameserver records with my registrar it rejects these domains. It seems that the .com TLD registrar (and possibly all TLDs?) only accept "well known" DNS servers, possibly from an IP address whitelist.
I happen to be trying to do this in AWS Route53, but it seems like the root problem is more fundamental than the limits of a particular registrar. The actual error reports are obtuse, but this support article seems to be suggest the reason why it might be failing.
I am not trying to implement a "vanity" DNS name using the same domain I want to resolve, so I don't think glue records are relevant. In any case, they only allow you to point at the IP address of an existing DNS server using a different domain name.
I need a custom DNS server because it will be translating domain names into IP addresses dynamically rather than from a static list.
Am I missing something obvious? I feel like this is pretty basic Internet plumbing albeit uncommon in today's service-rich environment.