1 Answer
- Newest
- Most votes
- Most comments
0
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>
Relevant content
- Accepted Answerasked 4 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 17 days ago
- AWS OFFICIALUpdated 9 months ago
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.