Connectivity Issues with Specific AWS Route53 NS Records (ns-512 to ns-1023.awsdns-XX.net)

Thank you for providing such detailed information about the connectivity issues you're experiencing with specific AWS Route 53 nameservers. While I don't have direct information about widespread issues affecting these specific nameservers, I can provide some insights based on how Route 53 private hosted zones work, which may be relevant to your situation.

In Route 53 private hosted zones, a set of specific nameservers are always used. These are:

• ns-0.awsdns-00.com
• ns-512.awsdns-00.net
• ns-1024.awsdns-00.org
• ns-1536.awsdns-00.co.uk

These nameservers are reserved for private hosted zones and are never used by Route 53 public hosted zones. It's important to note that while these nameservers are visible on the internet, Route 53 Resolver doesn't actually connect to these nameserver addresses for private hosted zones. Instead, it uses direct, private connectivity to reach the private DNS servers based on VPC to hosted zone associations.

Given that you're experiencing issues with nameservers in the range ns-512 through ns-1023 (specifically those with .net TLD), it's possible that there might be some confusion or overlap between private and public hosted zone configurations.

Regarding your questions:

1. While I don't have information about widespread issues, the behavior you're describing is not typical for Route 53 public hosted zones.

2. As a potential workaround, you could try creating a new hosted zone to see if you get assigned different nameservers. However, this may not be a practical solution if you have many existing records.

3. Unfortunately, there isn't a way to manually request specific nameserver assignments in Route 53. The nameservers are automatically assigned when you create a hosted zone.

Given the critical impact on your reverse DNS zones and the warning from JPNIC, I would strongly recommend contacting AWS Support directly. They will have access to more detailed information about your specific configuration and any potential issues affecting the nameservers in question. They may also be able to assist with reassigning nameservers if necessary.

In the meantime, ensure that your VPC configurations and Route 53 Resolver settings are correctly set up, especially if you're using both public and private hosted zones. Also, double-check that there are no conflicting firewall rules or network ACLs that might be blocking traffic to specific nameserver IP ranges.
Sources
Working with private hosted zones - Amazon Route 53