Questions tagged with Amazon Route 53

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Can not call HTTP API with Custom domain which provided by Google Domain

I'm going to connect HTTP API to my domain and use it. My domain is ***.art and I'm using it from Google. First, I connected CNAME to connect to AWS Amplify. Below is a captured copy of the Admin tab for the Amplify domain and the DNS settings status for the Google domain. ![Enter image description here](/media/postImages/original/IMB_v0nABCQlCCYiDg12-d2w) ![Enter image description here](/media/postImages/original/IMFAxZpx67SJuQywDFZY_7kQ) Subsequently, we created an HTTP API and verified calls through that URL.![Enter image description here](/media/postImages/original/IMvwgkwY8cT26mAvQkxWUziQ) The path and CORS settings of the API are shown in the screenshot below. ![Enter image description here](/media/postImages/original/IMgV_fMCrZTCmDIGUNWS_OYg)![Enter image description here](/media/postImages/original/IMiNitf33iQamWTYY5xe6QPQ) And the settings for the custom domain are as follows. ![Enter image description here](/media/postImages/original/IMbAtfy-xzStmVm9fP81rLBg) ![Enter image description here](/media/postImages/original/IMDBwuYv4gSV2Ro_3u-Yhz3A) Finally, the certificate and the DNS setting of the Google domain to which it was applied are as follows. ![Enter image description here](/media/postImages/original/IM6kXCEe7ZRiKUxDoIX4hkyA) ![Enter image description here](/media/postImages/original/IMSm3e45NJTMCJZW9Khrwvyw) I would appreciate it if you could tell me which part went wrong. The following is an error response when Chrome accessed the HTTP API address through my custom domain. ![Enter image description here](/media/postImages/original/IMWg1T0EeAQq-SgV5FTYm_dA) ![Enter image description here](/media/postImages/original/IM-KMgzjgITX-I3u_N-Lr5JQ)
0
answers
0
votes
23
views
asked a month ago

CNAME record problem

**What i have:** \ 2 accounts, first account is where i bought domain name = `company.com`, and where the hosted zone is setup-ed for that domain. Second account is where i request certificate in ACM for sub-domain name `test.company.com` from AWS. \ **The problem:** \ So, as i got ACM certificate, i need to validate it, to validate it, i need to create CNAME record in hosted zone of first account, with generated CNAME values. And this certificate is never validated... If i request a certificate in second account for `company.com` (same as main-domain name), then cert is validated.\ **A question:**\ How to create a sub-domain certificate, and validate it, if main-domain name hosted-zone is in another account? **Solutions that i have found:**\ solution mentioned here https://repost.aws/questions/QUYsz79cxKSCGtCrf0WyylMg/route-53-zone-hosted-on-two-accounts , is the only one? to create another hosted-zone, with sub-domain name, take the generated NS record value, and then create another NS record in the main-domain name hosted-zone with this value? and only then create a sub-domain certificate CNAME record in this sub-domain hosted-zone? Sounds like a lot of work, knowing that i want to automate all of that, as there will be 2 different accounts involved, multiple hosted-zones created, and a lot of CNAME and NS records managed. **P.S** Also, I only found a way to create an CNAME record via AWS CLI, NS record, as i understood is unavailable for creation via AWS CLI, what is another problem for my task.
1
answers
1
votes
42
views
asked a month ago

AWS DNS resolver replies with empty answer for query from docker container

Hello, I am investigating an issue with a docker container, run on a AWS Batch managed - EC2 environment, which is consistently failing to resolve "eu-central-1.wasabisys.com". When I demonstratively run a simple alpine container, I am not able to resolve the DNS record for "`eu-central-1.wasabisys.com`" whereas the record for "`us-central-1.wasabisys.com`" is working as expected. ```# docker run -it alpine / # nslookup eu-central-1.wasabisys.com. Server: 172.31.0.2 Address: 172.31.0.2:53 Non-authoritative answer: Non-authoritative answer: ``` I am successfully able to resolve the record on the host as well as with dig on the container, after installing it's package. This is a tcpdump captured on the host. In the beginning of the following snippet the resolution was done using nslookup (it contained no answers) and in the second try the same resolution was done using dig (it contained answers) 172.31.44.35 = Host IP 172.17.0.2 = Container IP 172.31.0.2 = AWS Resolver (automatically assinged) ```[root@ip-172-31-44-35 ec2-user]# tcpdump -nnevvvi any port 53 tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 15:53:09.235581 P 02:42:ac:11:00:02 ethertype IPv4 (0x0800), length 88: (tos 0x0, ttl 255, id 36324, offset 0, flags [DF], proto UDP (17), length 72) 172.17.0.2.60435 > 172.31.0.2.53: [bad udp cksum 0x587a -> 0x190b!] 14781+ A? eu-central-1.wasabisys.com. (44) 15:53:09.235600 In 02:42:ac:11:00:02 ethertype IPv4 (0x0800), length 88: (tos 0x0, ttl 255, id 36324, offset 0, flags [DF], proto UDP (17), length 72) 172.17.0.2.60435 > 172.31.0.2.53: [bad udp cksum 0x587a -> 0x190b!] 14781+ A? eu-central-1.wasabisys.com. (44) 15:53:09.235612 Out 0a:8c:33:66:0d:1e ethertype IPv4 (0x0800), length 88: (tos 0x0, ttl 254, id 36324, offset 0, flags [DF], proto UDP (17), length 72) 172.31.44.35.60435 > 172.31.0.2.53: [bad udp cksum 0x84a9 -> 0xecdb!] 14781+ A? eu-central-1.wasabisys.com. (44) 15:53:09.236215 In 0a:11:09:8b:8f:49 ethertype IPv4 (0x0800), length 88: (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 72) 172.31.0.2.53 > 172.31.44.35.60435: [udp sum ok] 14781| q: A? eu-central-1.wasabisys.com. 0/0/0 (44) 15:53:09.236220 Out 02:42:de:e4:72:cc ethertype IPv4 (0x0800), length 88: (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 72) 172.31.0.2.53 > 172.17.0.2.60435: [udp sum ok] 14781| q: A? eu-central-1.wasabisys.com. 0/0/0 (44) 15:53:09.236221 Out 02:42:de:e4:72:cc ethertype IPv4 (0x0800), length 88: (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 72) 172.31.0.2.53 > 172.17.0.2.60435: [udp sum ok] 14781| q: A? eu-central-1.wasabisys.com. 0/0/0 (44) [root@ip-172-31-44-35 ec2-user]# tcpdump -nnevvvi any port 53 tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 15:53:29.219638 P 02:42:ac:11:00:02 ethertype IPv4 (0x0800), length 111: (tos 0x0, ttl 255, id 9196, offset 0, flags [none], proto UDP (17), length 95) 172.17.0.2.50529 > 172.31.0.2.53: [bad udp cksum 0x5891 -> 0x120c!] 12676+ [1au] A? eu-central-1.wasabisys.com. ar: . OPT UDPsize=4096 (67) 15:53:29.219638 In 02:42:ac:11:00:02 ethertype IPv4 (0x0800), length 111: (tos 0x0, ttl 255, id 9196, offset 0, flags [none], proto UDP (17), length 95) 172.17.0.2.50529 > 172.31.0.2.53: [bad udp cksum 0x5891 -> 0x120c!] 12676+ [1au] A? eu-central-1.wasabisys.com. ar: . OPT UDPsize=4096 (67) 15:53:29.219665 Out 0a:8c:33:66:0d:1e ethertype IPv4 (0x0800), length 111: (tos 0x0, ttl 254, id 9196, offset 0, flags [none], proto UDP (17), length 95) 172.31.44.35.50529 > 172.31.0.2.53: [bad udp cksum 0x84c0 -> 0xe5dc!] 12676+ [1au] A? eu-central-1.wasabisys.com. ar: . OPT UDPsize=4096 (67) 15:53:29.220724 In 0a:11:09:8b:8f:49 ethertype IPv4 (0x0800), length 467: (tos 0x0, ttl 255, id 0, offset 0, flags [DF], proto UDP (17), length 451) 172.31.0.2.53 > 172.31.44.35.50529: [udp sum ok] 12676 q: A? eu-central-1.wasabisys.com. 23/0/1 eu-central-1.wasabisys.com. [20s] A 130.117.252.29, eu-central-1.wasabisys.com. [20s] A 130.117.252.26, eu-central-1.wasabisys.com. [20s] A 130.117.252.13, eu-central-1.wasabisys.com. [20s] A 130.117.252.18, eu-central-1.wasabisys.com. [20s] A 130.117.252.35, eu-central-1.wasabisys.com. [20s] A 130.117.252.16, eu-central-1.wasabisys.com. [20s] A 130.117.252.27, eu-central-1.wasabisys.com. [20s] A 130.117.252.20, eu-central-1.wasabisys.com. [20s] A 130.117.252.28, eu-central-1.wasabisys.com. [20s] A 130.117.252.23, eu-central-1.wasabisys.com. [20s] A 130.117.252.24, eu-central-1.wasabisys.com. [20s] A 130.117.252.12, eu-central-1.wasabisys.com. [20s] A 130.117.252.17, eu-central-1.wasabisys.com. [20s] A 130.117.252.31, eu-central-1.wasabisys.com. [20s] A 130.117.252.25, eu-central-1.wasabisys.com. [20s] A 130.117.252.21, eu-central-1.wasabisys.com. [20s] A 130.117.252.10, eu-central-1.wasabisys.com. [20s] A 130.117.252.11, eu-central-1.wasabisys.com. [20s] A 130.117.252.22, eu-central-1.wasabisys.com. [20s] A 130.117.252.34, eu-central-1.wasabisys.com. [20s] A 130.117.252.33, eu-central-1.wasabisys.com. [20s] A 130.117.252.19, eu-central-1.wasabisys.com. [20s] A 130.117.252.32 ar: . OPT UDPsize=4096 (423) 15:53:29.220734 Out 02:42:de:e4:72:cc ethertype IPv4 (0x0800), length 467: (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 451) 172.31.0.2.53 > 172.17.0.2.50529: [udp sum ok] 12676 q: A? eu-central-1.wasabisys.com. 23/0/1 eu-central-1.wasabisys.com. [20s] A 130.117.252.29, eu-central-1.wasabisys.com. [20s] A 130.117.252.26, eu-central-1.wasabisys.com. [20s] A 130.117.252.13, eu-central-1.wasabisys.com. [20s] A 130.117.252.18, eu-central-1.wasabisys.com. [20s] A 130.117.252.35, eu-central-1.wasabisys.com. [20s] A 130.117.252.16, eu-central-1.wasabisys.com. [20s] A 130.117.252.27, eu-central-1.wasabisys.com. [20s] A 130.117.252.20, eu-central-1.wasabisys.com. [20s] A 130.117.252.28, eu-central-1.wasabisys.com. [20s] A 130.117.252.23, eu-central-1.wasabisys.com. [20s] A 130.117.252.24, eu-central-1.wasabisys.com. [20s] A 130.117.252.12, eu-central-1.wasabisys.com. [20s] A 130.117.252.17, eu-central-1.wasabisys.com. [20s] A 130.117.252.31, eu-central-1.wasabisys.com. [20s] A 130.117.252.25, eu-central-1.wasabisys.com. [20s] A 130.117.252.21, eu-central-1.wasabisys.com. [20s] A 130.117.252.10, eu-central-1.wasabisys.com. [20s] A 130.117.252.11, eu-central-1.wasabisys.com. [20s] A 130.117.252.22, eu-central-1.wasabisys.com. [20s] A 130.117.252.34, eu-central-1.wasabisys.com. [20s] A 130.117.252.33, eu-central-1.wasabisys.com. [20s] A 130.117.252.19, eu-central-1.wasabisys.com. [20s] A 130.117.252.32 ar: . OPT UDPsize=4096 (423) 15:53:29.220737 Out 02:42:de:e4:72:cc ethertype IPv4 (0x0800), length 467: (tos 0x0, ttl 254, id 0, offset 0, flags [DF], proto UDP (17), length 451) 172.31.0.2.53 > 172.17.0.2.50529: [udp sum ok] 12676 q: A? eu-central-1.wasabisys.com. 23/0/1 eu-central-1.wasabisys.com. [20s] A 130.117.252.29, eu-central-1.wasabisys.com. [20s] A 130.117.252.26, eu-central-1.wasabisys.com. [20s] A 130.117.252.13, eu-central-1.wasabisys.com. [20s] A 130.117.252.18, eu-central-1.wasabisys.com. [20s] A 130.117.252.35, eu-central-1.wasabisys.com. [20s] A 130.117.252.16, eu-central-1.wasabisys.com. [20s] A 130.117.252.27, eu-central-1.wasabisys.com. [20s] A 130.117.252.20, eu-central-1.wasabisys.com. [20s] A 130.117.252.28, eu-central-1.wasabisys.com. [20s] A 130.117.252.23, eu-central-1.wasabisys.com. [20s] A 130.117.252.24, eu-central-1.wasabisys.com. [20s] A 130.117.252.12, eu-central-1.wasabisys.com. [20s] A 130.117.252.17, eu-central-1.wasabisys.com. [20s] A 130.117.252.31, eu-central-1.wasabisys.com. [20s] A 130.117.252.25, eu-central-1.wasabisys.com. [20s] A 130.117.252.21, eu-central-1.wasabisys.com. [20s] A 130.117.252.10, eu-central-1.wasabisys.com. [20s] A 130.117.252.11, eu-central-1.wasabisys.com. [20s] A 130.117.252.22, eu-central-1.wasabisys.com. [20s] A 130.117.252.34, eu-central-1.wasabisys.com. [20s] A 130.117.252.33, eu-central-1.wasabisys.com. [20s] A 130.117.252.19, eu-central-1.wasabisys.com. [20s] A 130.117.252.32 ar: . OPT UDPsize=4096 (423) ``` Has anybody any clue what is going on? Why is the AWS resolver not replying correctly? Thanks a lot for you help!
0
answers
0
votes
27
views
KniFFeL
asked a month ago