- Newest
- Most votes
- Most comments
The situation you're describing appears to be related to DNS resolution and routing within AWS services. The domain "ec2-52-6-251-20.compute-1.amazonaws.com/.hanssmedema.info" is not a standard or expected format, and it's likely causing issues due to a misconfiguration or unintended routing.
To address your questions:
-
This unusual domain format should not exist and is likely causing trouble because it's not a valid domain structure. The ".hanssmedema.info" part appears to be incorrectly appended to an EC2 public DNS name.
-
The reason your normal 'hanssmedema.info' works perfectly through Cloudflare is that Cloudflare is managing your DNS and routing correctly for that domain.
-
The "ec2-52-6-251-20.compute-1.amazonaws.com" part is an AWS EC2 public DNS name. It corresponds to an EC2 instance with the public IP 52.6.251.20. This should not be combined with your domain name as it appears in your example.
-
No, this combined domain does not have to be there and should not be there. It's likely a result of a misconfiguration in your DNS settings or routing rules.
To resolve this issue, you should:
- Check your Route 53 or other DNS settings to ensure there are no incorrect entries combining your domain with EC2 public DNS names.
- Review your EC2 instance configurations and any associated load balancers or other routing services to make sure they're correctly set up.
- Ensure that your domain is properly pointed to the correct AWS resources (like a CloudFront distribution or an ALB) rather than directly to an EC2 instance.
If you're using services like AWS Amplify or S3 for static website hosting, make sure your domain settings there are correct as well. If the issue persists, you may need to contact AWS support for further assistance in identifying and resolving the root cause of this unusual domain combination.
Sources
AWS Amplify re-domain mapping not allowed | AWS re:Post
Another account has hijacked my domain by creating a S3 bucket with the same name | AWS re:Post
Why is the final resolved result of domain name access not the public IP address of the EC2 instance? | AWS re:Post
Relevant content
asked 4 years ago
asked 2 months ago
asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a month ago
