1 Answers
0
Accepted Answer
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.
answered 3 years ago
Relevant questions
Route53 not finding nameserver publically
asked 2 years agoIn the midst of transferring all my domains to Route53 I have an important .UK.NET domain that I find I cant transfer to ROUTE53
Accepted Answerasked 4 months agoCan I use AWS as a nameserver without transferring my domain name registration?
Accepted Answerasked 8 days agoGitHub repository for Realtime Servers?
Accepted Answerasked a year agoUsing our own computing servers instead of Amazon servers?
Accepted Answerasked 3 years agocustom environment create one video for all test cases
asked 3 years agohiding name servers under my own ns
asked 3 years agoWorkmail Failing on iPhone for One User Account Only
asked 7 months agoOne Nameserver for all my servers
Accepted Answerasked 3 years agoDynamoDB ProjectionExpression exclude attribute (all fields except one)
asked 3 years ago