R53 Domain does not direct to my static IP anymore

Question

Hello all,

I'm new to aws and not very familiarized with technology either but I've managed to redirect the domain registered in R53 to my lightsail instance and static IP. It worked for some days but tt some point, after some days, for some reason it stop working and now I can only access my website through the static IP. Do you know what could have happened and how to fix it?

Website is www.roterseguros.com and fixed IP is http://54.158.189.135/

Thanks,
Martin.

Riku_Kobayashi · Accepted Answer

Hello.

When resolving "www.roterseguros.com", the IP address cannot be confirmed.
When resolving "roterseguros.com", the IP address can be confirmed.
Is the A record for "www.roterseguros.com" set up correctly in your Route53 hosted zone?

dig www.roterseguros.com

; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> www.roterseguros.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40613
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www.roterseguros.com.          IN      A

;; AUTHORITY SECTION:
roterseguros.com.       900     IN      SOA     ns-503.awsdns-62.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 10 msec
;; SERVER: 10.255.255.254#53(10.255.255.254) (UDP)
;; WHEN: Sun May 18 11:30:32 JST 2025
;; MSG SIZE  rcvd: 127

dig roterseguros.com

; <<>> DiG 9.18.30-0ubuntu0.24.04.2-Ubuntu <<>> roterseguros.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9614
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;roterseguros.com.              IN      A

;; ANSWER SECTION:
roterseguros.com.       300     IN      A       54.158.189.135

;; Query time: 229 msec
;; SERVER: 10.255.255.254#53(10.255.255.254) (UDP)
;; WHEN: Sun May 18 11:30:39 JST 2025
;; MSG SIZE  rcvd: 61

Martin · Answer

Hello All, 
I managed to correlctly setup the site following your suggestions and now it works properly. It seems that when directing R53 to lightsail DNS zone, servers were subsituted and the records were pointing at the older ones.
Thanks all for your answers and help.

Martin.

re:Post Agent · Answer

Based on your description, it sounds like you're experiencing a DNS issue with your Route 53 domain configuration. There are several potential reasons why your domain suddenly stopped directing to your static IP:

1. DNS Propagation: If you recently made changes to your DNS settings, it can take up to 48 hours for these changes to fully propagate across the internet. During this time, some users may be able to access your site while others cannot.

2. DNS Configuration: Double-check that your A record in Route 53 is correctly pointing to your Lightsail instance's static IP address (54.158.189.135). Ensure there are no typos or errors in the configuration.

3. Lightsail DNS Zone: Verify that you have created a DNS zone in Lightsail for roterseguros.com and that all necessary records are properly configured.

4. Name Servers: Ensure that the name servers listed in your domain registrar account match exactly with those provided by Route 53 for your hosted zone.

To troubleshoot and resolve this issue:

1. Verify all DNS records in Route 53 are correct, especially the A record pointing to your static IP.
    2. Check your domain's name servers using a WHOIS lookup tool to ensure they're set to the AWS name servers.
    3. Use online DNS propagation checkers to see if the issue is global or localized.
    4. Clear your local DNS cache and try accessing the site from different networks and devices.
    5. Review your Lightsail instance's firewall settings to ensure it's allowing incoming traffic on the necessary ports (typically 80 for HTTP and 443 for HTTPS).

If after checking these items the issue persists, you may want to contact AWS support for further assistance. They can help identify any potential misconfigurations in your Lightsail or Route 53 setup.
      
**Sources**  
[Suddenly the domain connection fails. | AWS re:Post](https://repost.aws/questions/QU0q3lfuzxR2GmkSy-ae0xKw/suddenly-the-domain-connection-fails)  
[Domain name not Pointing to Static IP | AWS re:Post](https://repost.aws/questions/QUFYXt6Vh3Q4mp3Z9V7c36Vg/domain-name-not-pointing-to-static-ip)

R53 Domain does not direct to my static IP anymore

Add your answer

Relevant content