2 ms·

In that event, AWS would respond by saying: The EC2 has responded, and informed me that they do not provide analysis of individual issues in AWS infrastruc

by 0xmohit 10y ago

In that event, AWS would respond by saying: The EC2 has responded, and informed me that they do not provide analysis of individual issues in AWS infrastructure. They referred to the AWS SLA that states that "AWS will use commercially reasonable efforts to make Amazon EC2 and Amazon EBS each available with a Monthly Uptime Percentage (defined below) of at least 99.95%". The AWS SLA is available here: https://aws.amazon.com/ec2/sla/ (The above is a part of the response I received when I attempted to ask AWS about sporadic reboots and outages on one of my instances.)

0xmohit 10y ago
Another gem from AWS in response to a query that mentioned that every major DNS server around the world had picked up a change made to the A record of a domain except for Amazon DNS (even after 2 hours of the change): Thanks for that information. It really help us understand the issue faced. As you know changing a A record for a domain can take time to replicate through all the Root DNS servers and then onto the none authoritative servers from there on. When you are editing your DNS Zone file it is highly related to the TTL settings for quicker updates on changes to them. However it really isn't uncommon to see full DNS replication when making changes to an A record. .. Also for even more control and perhaps faster DNS resolving times within AWS look into our Route53 service. https://aws.amazon.com/route53/ I hope this has addressed your questions and please feel free to ask if there is anything else. Tools like http://mxtoolbox.com/dnspropagation.aspx http://mxtoolbox.com/dnspropagation.aspx and http://www.viewdns.info/propagation/ http://www.viewdns.info/propagation/ indicated that the change had been picked up by every listed server but for AWS. Solution proposed by AWS: Use Route53.

by 0xmohit 10y ago

0xmohit 10y ago

Another gem from AWS in response to a query that mentioned that every major DNS server around the world had picked up a change made to the A record of a domain except for Amazon DNS (even after 2 hours of the change): Thanks for that information. It really help us understand the issue faced. As you know changing a A record for a domain can take time to replicate through all the Root DNS servers and then onto the none authoritative servers from there on. When you are editing your DNS Zone file it is highly related to the TTL settings for quicker updates on changes to them. However it really isn't uncommon to see full DNS replication when making changes to an A record. .. Also for even more control and perhaps faster DNS resolving times within AWS look into our Route53 service. https://aws.amazon.com/route53/ I hope this has addressed your questions and please feel free to ask if there is anything else. Tools like http://mxtoolbox.com/dnspropagation.aspx http://mxtoolbox.com/dnspropagation.aspx and http://www.viewdns.info/propagation/ http://www.viewdns.info/propagation/ indicated that the change had been picked up by every listed server but for AWS. Solution proposed by AWS: Use Route53.