Having a single nameserver generally is not something you would want to do, and not something that ISPs recommend. It means that when your website is being queried, only a single server would serve up the underlying dns information: If that server went down, your systems would not be availalbe to end users trying to get to your website.
It seems like what you want to do is have your clients put in a CNAME record for their website to point to the DNS name of your load balancer. the load balancer would then be responsible for distributing traffic to the underlying EC2 or non-EC2 environments.
Route53 not finding nameserver publicallyasked 2 years ago
In the midst of transferring all my domains to Route53 I have an important .UK.NET domain that I find I cant transfer to ROUTE53Accepted Answerasked 4 months ago
Can I use AWS as a nameserver without transferring my domain name registration?Accepted Answerasked 8 days ago
GitHub repository for Realtime Servers?Accepted Answerasked a year ago
Using our own computing servers instead of Amazon servers?Accepted Answerasked 3 years ago
custom environment create one video for all test casesasked 3 years ago
hiding name servers under my own nsasked 3 years ago
Workmail Failing on iPhone for One User Account Onlyasked 7 months ago
One Nameserver for all my serversAccepted Answerasked 3 years ago
DynamoDB ProjectionExpression exclude attribute (all fields except one)asked 3 years ago