1.1.1.1 not resolving valid domain

Hi everyone,
I’ve been using 1.1.1.1 as a resolver on company level, and we came across what 1.1.1.1 is not resolving groovehiring.com domain for our client. other public dns’s does.
Anyone have an idea ? I wouldn’t like to change it as a primary resolver…

The domain is using Dynadot’s DNS service, which seems to be working unreliably today.

This thread was also talking about it:

I can resolve that domain using 1.1.1.1 sometimes.

Thanks.

There was also some mention of it on Dynadot’s Twitter account:

https://twitter.com/Dynadot/with_replies

Seems like they were getting DDoSed.