Questions tagged with Domain Name System (DNS)
Sort by most recent
Browse through the questions and answers listed below or filter and sort to narrow down your results.
Why doesn't my hosted zone A record resolve correctly for an .io domain?
I have several hosted zones on .com and .us domains and they all work fine. I have root and sub-domains setup. However, when I add an A record for my .io domain, it will not resolve to the IP address. I'm not new to this, have used many registrars over the years, but this baffles me. I tried deleting the hosted zone and creating a new one, and I have also waited 24+ hours, but still no dice. Any suggestions?
SES Ip Blacklisted in Spamhaus
According to Q4 of https://docs.aws.amazon.com/ses/latest/dg/faqs-dnsbls.html, when one of SES Ip address used by AWS falls into a DNSBL like spamhaus, AWS itself takes action to remove it from the list. Recently we've noticed a lot of messages falling into spam when using one of the ips in range 54.240.3.X. When checking it on spamhaus we were able to see that since 2022/07/17 this ip range is listed as spam. I'd like to know when will AWS take action to move this ip out of this DNSBL or if it is possible to assign another ip range to send the emails.
API Gateway > Custom Domain Name > TooManyRequestsException
I have just created a HTTP API and would like to setup a custom domain name *somedomain.mysite.com* In Console under Create Domain Name, when I select mutual TLS option and enter truststore URI in S3, using ACM public certificate which I have requested earlier for same domain name, there is an error of Too Many Requests. Under Route53, there is an A record pointing to *somedomain.mysite.com* and a CNAME record to validate the DNS for the certificate under same domain. Using the certificate ARN, I have copied the certificate chain as a PEM file and uploaded to S3 I'm not sure where is the exception coming from as I have not done any updates on API Gateway so far
Debugging DNS lookup of MariaDB instance.
Hi. My serverless instance in AWS can reach my MariaDB database (RDS) and things work fine but things don't work if I try to connect from my local computer. The problem appears and disappears randomly, It works some days and it doesn't work on other days. Here is the result of ping to MYDB.eu-west-1.rds.amazonaws.com ``` PING MYDB.eu-west-1.compute.amazonaws.com (188.8.131.52) 56(84) bytes of data. ---MYDB.eu-west-1.compute.amazonaws.com ping statistics --- 13 packets transmitted, 0 received, 100% packet loss, time 12448ms ``` Here is what it looks like if I connect with PMA in a docker container: ![Enter image description here](https://repost.aws/media/postImages/original/IMF16lOoiyTbGhuqcAm781tA) I tried to reboot the DB. Is there something else I should try?
Amazon Route53 Geolocation Routing Failover
Hi guys! I consider using Route53 with Geolocation routing to redirect my users traffic to my application hosted in two different Regions (Singapore and Japan). The reason I use Geolocation is that I want to redirect my user traffic to their language. The app is Singapore region is English and the app host in Japan region is for Japanese. Route53 with Geolocation will redirect user from Japan to their local region. On the other hand, user from other countries will be redirected to Singapore region. I have a question that if the Singapore region is down, will users be redirected to Japan region automatically?
How and When would domain name would publicly available on the internet ?
I have purchased the domain name from Route 53 AWS. created the hosted zone in DNS. Launched EC2 instance with AMI WordPress. Allocated the Elastic IP address with the EC2 instance Created the A-type record in the hosted zone with the public IP addresses. Are there any other steps I have to follow?
DNS Problem specific domains
We have problems with resolving jtl-software.com. We get a timeout if we resolve against 10.0.0.2 (our internal AWS DNS server), but not against 184.108.40.206. Other domains are resolved by 10.0.0.2 but we dont know that the problem is. Maybe an internal aws issue. Hope somebody can help us with this problem! Kind regards Marc
Cloudflare DNS not accepting my AWS Workmail MX Value
I am moving my email away from godaddy to AWS workmail for my domain. My domain is still registered at godaddy with DNS at Cloudflare. I get the following error message "DNS Validation Error (Code: 1004) Content for MX record must be a hostname." When adding the MX value given my AWs workmail to my cloudflare DNS. Below is the value from from AWS. 10 inbound-smtp.us-east-1.amazonaws.com.
DNS A, CNAME records and ELB
Hello, i have some websites hosted behind ELB on autoscaling group. On my externals domain registrar (it can be namebay, ovh, whatever...) : - i set CNAME www (www.domain.tld) to ELB name - i set A (domain.tld) to my proxy server EC2+ip static then iptables redirects to my ELB. - SSL certificates are distributed by EC2 instance autoscaling group behing ELB everything works nearly perfectly but i find it very complicated to manage and i'd like a way to remove my proxy instance to manage everything on domain registrar is there a better way to proceed ?
AWS Lightsail - PTR & SMTP
Hi Guys New to AWS Lightsail. I have created a WordPress instance with Lightsail. I need some help as I am new and not very savvy in this case. The I have associated a static IP to the WordPress site and it is running fine. I am having some issue with email rejection and not sure why. Something to do with PTR and SMTP. The domain is pointing to Office 365 Email using "Microsoft" Name Servers. Basically they are hosting the DNS records, from there the domain is pointing to Lightsail instance using and IP "A" Record. That is all. Now I just want to know if this cause any issues and or if I need to implement anything else also who to use PRT and where. Appreciate any help in advance. Ben