How to use Route 53 when static IP addresses are required for DNS Name Servers?

When dealing with a domain registrar that requires static IP addresses for name servers, you have a few options to work with Route 53:

1. White-label name servers (vanity name servers): Route 53 allows you to configure white-label name servers, which let you use custom domain names for your name servers (like ns1.yourdomain.com). While the underlying IP addresses are still Amazon's anycast IPs, this approach might satisfy some registrars since you'd be providing your own domain's name servers.

2. Use Route 53's name server IP addresses: Although Route 53 uses anycast IP addresses that can change, you could obtain the current IP addresses of the Route 53 name servers assigned to your hosted zone. However, this is not recommended as a long-term solution since these IPs may change over time.

3. Self-hosted DNS solution: If the registrar strictly requires static IPs, you could set up your own DNS servers on EC2 instances with Elastic IPs. You would then:

• Launch EC2 instances with DNS server software (like BIND)
• Assign Elastic IPs to these instances
• Configure them to serve your DNS records
• Register these static IPs with your domain registrar

4. Consider a different registrar: The most straightforward solution might be to use a registrar that accepts name server hostnames rather than requiring static IPs, as this requirement is somewhat uncommon in modern DNS setups.

AWS does not provide static IPs specifically for Route 53 name servers, as the service is designed to use Amazon's global anycast network for high availability and performance. The white-label name server approach is the closest native Route 53 solution, though it still uses Amazon's dynamic IP infrastructure behind the scenes.
Sources
Configuring white-label name servers - Amazon Route 53
DNS redirection via route 53 hosted zone | AWS re:Post
Route53: Can we point to Route53 name servers vs our existing for testing DNS records? | AWS re:Post