For the most recent update on ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1), refer to the AWS Health Dashboard. For information on AWS Service migration, see How do I migrate my services to another region?
Rout 53 Don't Work
Hello I transfer my domain to AWS And also make Hosted Zone and write the name servers of rout 53 in My registered Domain and it work for 3 day's and stop working after that , I am doing the following steps :
1-Delete the hosted Zone and Make New One And change the old Name Servers 2- Make A record and point it to my Elastic IP ( Not Working ) 3- Make A record And point it to Classic Load Balancer (Not Working ) 4- Make account at (No-IP web Site ) and Make host name pointed to my Elastic IP ( Working Good ) 5- The IP is Reachable And the Public IPv4 DNS also working fine
can any one help me please ?
- Newest
- Most votes
- Most comments
The errors indicate that CURL is failing due to being unable to validate the SSL certificate because it is self-signed. To have CURL ignore certificate errors/warnings, use "-k" or "--insecure"; instead of -i. You could also disable curl SSL verification, by default, for ALL use cases, by entering this command: $ echo insecure >> ~/.curlrc
Hello.
Is it possible to resolve names of NS records using the "dig" command?
I recommend troubleshooting using the steps outlined in the following documents:
https://repost.aws/knowledge-center/route-53-dns-website-unreachable
dig domain.com
thanks for replay i am already doing dig and also dns checker and i found the domain is belong to the right Name servers for rout 53 - i upload screen shots for dig and dns checker
In my environment, the name resolution is possible with the "dig" command, so there may be a problem with your network or the DNS server you are using.
dig wassalats.com ; <<>> DiG 9.16.1-Ubuntu <<>> wassalats.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63905 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;wassalats.com. IN A ;; ANSWER SECTION: wassalats.com. 60 IN A 54.215.115.10 wassalats.com. 60 IN A 50.18.208.1 ;; Query time: 156 msec ;; SERVER: 192.168.11.1#53(192.168.11.1) ;; WHEN: 日 8月 11 21:52:27 JST 2024 ;; MSG SIZE rcvd: 74Although I am accessing from Tokyo, I was able to confirm that it is working normally. So please try accessing from another network or PC.
curl https://wassalats.com -i HTTP/2 200 date: Sun, 11 Aug 2024 12:54:49 GMT content-type: text/html;charset=UTF-8 content-length: 1142 server: Apache/2.4.52 (Ubuntu) vary: Accept-Encoding <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html> <head> <title>Index of /</title> </head> <body> <h1>Index of /</h1> <table> <tr><th valign="top"><img src="/icons/blank.gif" alt="[ICO]"></th><th><a href="?C=N;O=D">Name</a></th><th><a href="?C=M;O=A">Last modified</a></th><th><a href="?C=S;O=A">Size</a></th><th><a href="?C=D;O=A">Description</a></th></tr> <tr><th colspan="5"><hr></th></tr> <tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="html/">html/</a></td><td align="right">2023-08-31 22:30 </td><td align="right"> - </td><td> </td></tr> <tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="ts/">ts/</a></td><td align="right">2024-08-03 09:15 </td><td align="right"> - </td><td> </td></tr> <tr><td valign="top"><img src="/icons/folder.gif" alt="[DIR]"></td><td><a href="wassalat.store/">wassalat.store/</a></td><td align="right">2023-09-01 19:48 </td><td align="right"> - </td><td> </td></tr> <tr><th colspan="5"><hr></th></tr> </table> <address>Apache/2.4.52 (Ubuntu) Server at wassalats.com Port 443</address> </body></html>Where are you running the curl command from? Are you running it from your PC? If you are running from EC2 etc., please check if there are any special settings such as DNS settings (/etc/resolv.conf). Please check the DNS settings of the terminal running the curl or dig commands to see if "wassalats.com" is pointing to 127.0.0.1 (localhost).
@Riku_Kobayashi thanks for replay i am doing curl put the result is deferent i don't know the reason
thanks all for Replay's i solved the problem by the following : 1- i make an LoadBalancer and linked the ssl with the loadBalaner Target Group with ports 80 & 443-For-ssl 2- pointed the A record in Rout 53 ( Alias to Application Or Classic LoadBlancer) 3- Wait About 15 Minutes and The site is working fine
Relevant content
- asked 5 months ago
- AWS OFFICIALUpdated 3 years ago
@randy_weinstein thanks for replay i accepted your answer its may solve the problem with other person - it work fine if i dont have loadbalancer