We had faced a UDP attack on a few of our DNS management IPs causing our DNS caching mechanism to fail. In such a scenario the DNS traffic is served directly from our DNS servers. Concurrently, there was a load on one of the DNS database clusters due to which DNS traffic could not be served. In order to mitigate the attack, the affected IPs were mitigated. Once the database cluster recovered we made changes to the server firewall configuration to restore the services. We have identified the affected touchpoints and necessary measures have been taken to avoid similar events in the future.
Our System Administration team has fixed this issue. All the services have been restored and any services dependent on the default Orderbox Nameservers (partially and fully branded) should work seamlessly. We will share an RCA as soon as possible.
We are currently facing an issue with our default Orderbox Nameservers. Domains that are currently pointing to default Orderbox Nameservers may face intermittent issues with website resolution or any services that are dependent on the DNS.
The System Administration team has already been alerted and work is underway to get this issue resolved at the earliest.