[dns-operations] s3.amazonaws.com problem?

[abang]

Same here (AS3320), it works partial

;; AUTHORITY SECTION:
amazonaws.com.          3600    IN      NS      r1.amazonaws.com.
amazonaws.com.          3600    IN      NS      r2.amazonaws.com.
amazonaws.com.          3600    IN      NS      u1.amazonaws.com.
amazonaws.com.          3600    IN      NS      u2.amazonaws.com.

u1 and u2 are still dropping queries with 8 characters in the prefix 
(xxxxxxxx.s3.amazonaws.com). While r1 and r2 are responding.

Winfried



Am 23.10.2019 um 11:41 schrieb sthaug at nethelp.no:
>>> Is anyone else experiencing resolution issues for names in this domain? We are seeing a lot of queries of the form:
>>> CNAME? bvusfvyq.s3.amazonaws.com
>>> (the label before ".s3" looks random) and a lot of SERVFAIL responses.
>>>
>>> Any clues would be appreciated.
>> If you believe The Register (I know, I know...) Amazon’s DNS infrastructure is/was the target of a DDoS attack.
>> 	https://www.theregister.co.uk/2019/10/22/aws_dns_ddos/
> And Amazon *claims* the problems are resolved:
>
>      https://status.aws.amazon.com/
>
> "[RESOLVED] Intermittent DNS Resolution Errors
> Between 10:30 AM and 6:30 PM PDT, we experienced intermittent errors
> with resolution of some AWS DNS names. Beginning at 5:16 PM, a very
> small number of specific DNS names experienced a higher error
> rate. These issues have been resolved."
>
> However, the SERVFAIL statistics from our resolvers indicate that the
> problem is very much ongoing still.
>
> Steinar Haug, AS2116
>
> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations