AWS Lightsail domain does not resolve

0

Hello, I have a problem with Lightsail DNS and I would appreciate some help on this. These are the steps I have followed until now:

  1. I created an instance on Lightsail and attached a static IP to it.
  2. I deployed a website on the instance and I am able to access it through the static IP.
  3. Then I registered a domain ("amentes.es") through Route 53 (since the TLD ".es" was not available to be registered directly with Lightsail). I did NOT created a hosted zone in Route 53 since I want to manage it with Lightsail DNS zones.
  4. I created a DNS zone in Lightsail, and created an A record with name "@.amentes.es" routing traffic to the static IP. I also changed the domain NameServers to match the DNS zone ones.

My problem is that I can access the website through the static IP, but accessing "http://amentes.es" cannot resolve the IP (DNS_PROBE_FINISHED_NXDOMAIN error). I also tried to ping the domain but it returns an error (Temporary failure in name resolution).

This is the screen of the domain at Route 53:

Enter image description here

These are the DNS zone Name servers:

ns-1474.awsdns-56.org
ns-538.awsdns-03.net
ns-1558.awsdns-02.co.uk
ns-101.awsdns-12.com

This is the static IP: Enter image description here

And this is the screen with the records of the DNS zone in Lightsail: Enter image description here

I would appreciate if someone could tell me if I've missed something or there is something I can try to debug the problem. Thanks!

cbailon
demandé il y a 9 mois469 vues
1 réponse
0
Réponse acceptée

Hello.

I did not get "DNS_PROBE_FINISHED_NXDOMAIN" in my environment.
We also confirmed that the IP address is tied to the domain.
The request method may be incorrect because of the 400 error.

nslookup amentes.es
Server:         192.168.11.1
Address:        192.168.11.1#53

Non-authoritative answer:
Name:   amentes.es
Address: 3.79.177.221

curl http://amentes.es/
<!doctype html>
<html lang="en">
<head>
  <title>Bad Request (400)</title>
</head>
<body>
  <h1>Bad Request (400)</h1><p></p>
</body>
</html>
profile picture
EXPERT
répondu il y a 9 mois
profile picture
EXPERT
vérifié il y a 9 mois
profile pictureAWS
EXPERT
vérifié il y a 9 mois
  • Thank you so much for your quick response. It seems that I just had to wait for the DNS to propagate.

    The problem now is that I am able to access to the webpage using my mobile phone connected to the mobile network, but not if connected through my WiFi (shows the same resolution error as before). Could it be possible that the router has a DNS cache or similar?

  • I think there is a possibility that cache remains on the router or the PC you are using.

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions