Kim.ns.cloudflare.com not answering queries for some locations

Starting from 28th June 2018 around GMT 23:00, my authoritative name server kim.ns.Cloudflare.com did not respond to queries. I experienced this problem at 4 of my Internet uplinks in Hong Kong and 1 of my Azure VMs in Singapore. Host command returns this:
;; connection timed out; trying next origin
I could ping kim and get replies, however.

Do you get the same problem?

Hi,

Yes, we are unable to get to one of our authoritative name server ‘alla.ns.Cloudflare.com’ from Australia.

dig @alla.ns.Cloudflare.com

; <<>> DiG 9.10.6 <<>> @alla.ns.Cloudflare.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Unable to log a support ticket either, keeps wanting me to re-login to Cloudflare which I do, then search the Help Center, then click to submit a ticket and then loops…

I open a ticket and received a response that for our dns server this was a mitigation to DNS attacks.

Apparently adding +norec to dig (i.e. dig +norec @kim.ns.Cloudflare.com HOSTNAME.COM) should still work even when the DNS attack mitigation is in place.

Also see CloudFlare authoritative name servers not responding - #5 by cs-cf

1 Like

The problem is cleared at around 29th June GMT 3:00. Thank you mrowell.
BTW, it seems I have a bad memory.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.