AWS eks documentation change
Summary
Removed section about DNS resolution conflicts with .local domains in Route53 private hosted zones
Security assessment
The removed content was a DNS configuration best practice warning, not directly related to security vulnerabilities or incidents. No evidence of security issue remediation or exposure.
Diff
diff --git a/eks/latest/userguide/auto-troubleshoot.md b/eks/latest/userguide/auto-troubleshoot.md index 069de82f5..8278f3cdd 100644 --- a//eks/latest/userguide/auto-troubleshoot.md +++ b//eks/latest/userguide/auto-troubleshoot.md @@ -5 +5 @@ -Node monitoring agentGet console output from an EC2 managed instance by using the AWS EC2 CLIGet node logs by using debug containers and the kubectl CLIView resources associated with EKS Auto Mode in the AWS ConsoleView IAM Errors in your AWS accountTroubleshoot Pod failing to schedule onto Auto Mode nodeTroubleshoot node not joining the clusterSharing Volumes Across PodsDNS Resolution of Route53 private hosted zones with .local DomainsTroubleshoot included controllers in Auto Mode +Node monitoring agentGet console output from an EC2 managed instance by using the AWS EC2 CLIGet node logs by using debug containers and the kubectl CLIView resources associated with EKS Auto Mode in the AWS ConsoleView IAM Errors in your AWS accountTroubleshoot Pod failing to schedule onto Auto Mode nodeTroubleshoot node not joining the clusterSharing Volumes Across PodsTroubleshoot included controllers in Auto Mode @@ -285,6 +284,0 @@ To enable this sharing between Pods, you can use the Pod’s `seLinuxOptions` to -## DNS Resolution of Route53 private hosted zones with `.local` Domains - -If you configure a Route 53 private hosted zone using a `.local` suffix (e.g. `mydomain.local`), it will fail to resolve on EKS Auto Mode Nodes. You will need to use a different suffix for the Route 53 private hosted zone. - -It’s a general best practice to not use the domain name ".local" for Route 53 private hosted zones. RFC 6762 reserves this domain name for exclusive Multicast DNS use. For more information, see [Multicast DNS](https://datatracker.ietf.org/doc/html/rfc6762) on the Internet Engineering Task Force (IETF) website. The use of this name interferes with DNS Resolution as it leads to attempting to resolve the name via Multicast DNS instead of forwarding the query to the VPC resolver endpoint. -