Yeah - I have just been able to mitigate by exporting to route53 (via their system) and then adding the additional route53 dns servers to the root chain. Ugh :(
Fortunately for me I had the aws identity already setup and just had to do a new "export" to update the records.
Comments
is there anything we can do right now, to fix this problem while the attack is under way?
Yeah - I have just been able to mitigate by exporting to route53 (via their system) and then adding the additional route53 dns servers to the root chain. Ugh :(
Fortunately for me I had the aws identity already setup and just had to do a new "export" to update the records.