Forum Discussion

julianmaze's avatar
julianmaze
New Contributor
2 months ago

Issues with Cloudflare's DNS and NTP services

As of a few weeks ago, I have been experiencing issues utilizing Cloudlfare's public DNS resolver, 1.1.1.1, and NTP server, time.cloudflare.com. 

As for DNS, queries against 1.1.1.1 will not resolve, and return an error listing that the DNS request has timed out. Alternatively, queries against Google's DNS work just fine. 

> nslookup google.com 1.1.1.1
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  1.1.1.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

> nslookup google.com 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    google.com
Addresses:  2607:f8b0:4007:818::200e
          142.250.217.142

NTP is not much better, I simply cannot utilize time.cloudflare.com causing a few machines on my LAN to lose time synchronization. 

> ping time.cloudflare.com
Pinging time.cloudflare.com [162.159.200.1] with 32 bytes of data:
Request timed out.
Ping statistics for 162.159.200.1:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),

> ping one.one.one.one
Pinging one.one.one.one [1.1.1.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Here are some traceroutes to show that this traffic is indeed leaving my LAN.

> tracert 1.1.1.1
Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  10.50.70.20
  2    17 ms    17 ms     7 ms  10.139.96.1
  3     *        *        *     Request timed out.
  4    14 ms    12 ms    12 ms  68.1.4.108
  5    14 ms    16 ms    13 ms  172.68.228.82
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.

> tracert time.cloudflare.com
Tracing route to time.cloudflare.com [162.159.200.1]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  10.50.70.20
  2    11 ms    13 ms    10 ms  10.139.96.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *       36 ms    15 ms  72.215.224.171
  7    15 ms    15 ms    18 ms  162.158.184.3
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.

Is anyone else experiencing this issue? Any insight is appreciated, thanks.

2 Replies

    • julianmaze's avatar
      julianmaze
      New Contributor

      Maybe, but the nearest cloudlfare site to my physical location (San Diego) is operational according to the status page. I am still experiencing the issue as of today.