Do we have any source for the current title claim ("FAA DNS is under attack")?
What we have observed so far is intermittent issues but no root cause or intent. Operator error / system failure look more likely.
What we have observed so far is intermittent issues but no root cause or intent. Operator error / system failure look more likely.
If I had to guess randomly at a cause, I would speculate that all their nameservers besides 155.178.199.16 are behind a load balancer that uses checking for IN A faa.gov as a health check and someone deleted that record, so, all servers fell out of the load balancer.
50c says that their method of propagating new records relies on their DNS working so someone is having a fun night fixing that.