I got this today:

C:\Users\me>nslookup box.duckdns.org
Server:  1dot1dot1dot1.cloudflare-dns.com

*** 1dot1dot1dot1.cloudflare-dns.com can't find box.duckdns.org: Server failed

C:\Users\me>nslookup box.duckdns.org
Server:  google-public-dns-a.google.com

Non-authoritative answer:
Name:    box.duckdns.org

I would expect these two nameserver to return the same answer, yet they don't. Is that a problem on Cloudflare's DNS service, or do I misunderstand anything?

I should add that other domains resolve fine on both DNS servers.

  • 1
    This answer seems to cover your case. The answer uses the Linux dig command and this link shows how to implement it in Windows. – AFH Aug 12 '18 at 14:34
  • 1
    @AFH dig +trace doesn't use system wide DNS, but pretending to be a name server itself and starts resolving on its own beginning from root DNS servers bypassing CloudFlare free DNS at completely. I already point it out in comments that resolving FQDN box.duckdns.org isn't an issue for those who runs own DNS or used The issue is obviously at – Alex Aug 13 '18 at 13:38

Why does Cloudflare's DNS not resolve some DuckDNS domains, while Google's does?

Because CloudFlare had some needs to change it.(Technical issue, DDoS, mistake...)
BTW, I had similar issue with Google's public DNS. It shouldn't be for a long time, usually it is an issue in DNS propagation when some name server doing upgrade, mistake and so on... Both Google and CloudFlare public DNS are forwarding servers that gather information from name servers that are responsible for some particular zone.

Instead of using hard-coded IP address you better have to use in such cases one of official name servers that serves duckdns.org zone, which are:


nslookup box.duckdns.org ns2.duckdns.org

I suggest to switch temporary your system wide DNS either to until propagation/misconfiguration issue wouldn't be resolved at CloudFlare or use your ISP provider's DNS or simply use gateway/router IP that must automatically use ISP's DNS if you are on DHCP.

  • nslookup box.duckdns.org ns2.duckdns.org Well, guess what happens then ;) my (system-wide) Cloudflare DNS server cannot find an IP to that nameserver... – bers Aug 12 '18 at 11:54
  • 1
    So, that's obviously something wrong with DNS propagation at CloudFlare. I just queried from three different VPS that located in Germany, USA and Singapore and all three can't resolve box.duckdns.org via, while dedicated DNS servers that works on all of those VPS that aren't caching DNS but used resolving starting from root DNS servers, was able to resolve domain in question. – Alex Aug 12 '18 at 12:10
  • Actually when you running nslookup box.duckdns.org ns2.duckdns.org then nslookup bypassing system-wide DNS and query directly ns2.duckdns.org. It is possible that your ISP(or your antivirus, firewall) blocking request to remote 53 port. I did dig box.duckdns.org @ns2.duckdns.org and it resolved as it should. The same success for dig ns2.duckdns.org a – Alex Aug 12 '18 at 12:15
  • I expected this not to take too long, either. Nonetheless, the problem is still ongoing, so I doubt this is a temporary flaw and switched back to Google's DNS service... As to your suggestion using to "query directly ns2.duckdns.org" - well, I still need a DNS service to resolve the nameserver itself, and Cloudflare does not resolve ns2.duckdns.org. So much about not hardcoding IP addresses ;) – bers Aug 13 '18 at 13:20
  • 1
    Cloudflare DNS also does not resolve archive.is, apparently due to a misconfiguration by archive.is. Maybe Cloudflare DNS handles stuff unlike other servers. – Daniel B Aug 13 '18 at 13:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.