Amazon Route 53域名突然变为停放状态该如何排查？

Hey there, let's walk through the common issues that could be causing your domain to redirect to a parking page even when your EC2 is up and your Route 53 A record looks correct. Here are the key things to check:

• Verify your domain's name servers match Route 53's hosted zone
  This is the #1 culprit for this kind of issue. When you set up a Route 53 hosted zone, it assigns a set of 4+ name servers (NS records). You need to make sure these exact name servers are configured at your domain registrar—even if you registered the domain through Route 53, double-check the "Name servers" section in the Route 53 Domains console. A single typo here will cause your domain to use the registrar's default DNS, which often points to parking pages.

• Flush DNS caches (local and ISP)
  Your local machine or internet service provider might still be caching an old DNS record that points to the parking page. Test this by running:

  • On Windows: ipconfig /flushdns
  • On macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
    Then run nslookup yourdomain.com or dig yourdomain.com to confirm the returned IP matches your EC2's public IP. If it still doesn't, try accessing the domain from a different network (like a mobile hotspot) to rule out ISP-level caching.

• Check the TTL value on your Route 53 A record
  If your A record had a long TTL (e.g., 86400 seconds / 24 hours), DNS servers across the internet might take hours to update to the correct record. For debugging, you can temporarily lower the TTL to 300 seconds (5 minutes) to speed up propagation, then set it back once the issue is resolved.

• Look for conflicting DNS records in Route 53
  Double-check your Route 53 hosted zone for any other records that might override your A record. For example:

  • A CNAME record for your root domain (which conflicts with A records)
  • An Alias record pointing to a parking service or incorrect resource
  • A wildcard record (*.yourdomain.com) that might be intercepting traffic

• Confirm your domain's status is active
  Head to the Route 53 Domains console to check if your domain is in an active state. Look for flags like PendingVerification, Locked, or Expired—even if it worked before, a recent renewal issue or accidental lock could cause this problem.

• Rule out EC2 network configuration edge cases
  While you can access the EC2 via IP, double-check your security group and network ACL to ensure they allow incoming HTTP/HTTPS traffic (ports 80/443) from all IPs (or at least your test clients). This is less likely since IP access works, but it's a quick check to eliminate all possibilities.

内容的提问来源于stack exchange，提问作者ZbadhabitZ