A and CNAME records not working?

Hello.

Looking at the image you shared, the A record is registered as "@.notearama.com", but the "@" mark is not allowed in the domain name.
In other words, if you want to create an A record called "notearama.com", you can create it without entering anything in the record name.
Leave Record name blank and click "Create records" as shown in the image below.

Based on the information provided, there are a few potential issues that could be preventing your website from loading:

1. DNS Propagation: DNS changes can take up to 24-48 hours to propagate globally. If you've recently made these changes, you may need to wait longer for them to take effect.

2. Name Server Configuration: Ensure that the name servers (NS records) in your domain registrar account exactly match those provided by Route 53 for your hosted zone. This is a critical step that's often overlooked.

3. Record Configuration: Double-check that your A record is pointing to the correct IP address of your web server, and that your CNAME records are correctly set up.

4. TTL Values: The Time-to-Live (TTL) values for your records are set to 300 seconds (5 minutes). While this is generally fine, you might consider temporarily lowering this value to allow for faster propagation during your initial setup and troubleshooting.

5. Web Server Configuration: Ensure your web server is properly configured to handle requests for your domain name.

6. Security Groups and Firewall: If you're using an EC2 instance, check that your security groups allow incoming traffic on port 80 (HTTP) and 443 (HTTPS).

To troubleshoot further:

1. Use DNS lookup tools like 'dig' or 'nslookup' to verify that your records are resolving correctly.
2. Check if you can access your website using the IP address directly.
3. Verify that there are no errors in your web server's error logs.

If after checking these items and waiting for propagation your site still doesn't load, you may need to review your overall DNS and web server setup more thoroughly.
Sources
CNAME Records not being found | AWS re:Post
route53 problem | AWS re:Post
Domain name not resolving | AWS re:Post