1.1.1.1 issues with Hathway (India)


#1

I’m having issues with using 1.1.1.1 with Hathway in India. However 1.0.0.1 appears to work. The following logs should make the issue apparent.

Summary
PS D:\Users\shant> dig google.com

; <<>> DiG 9.10.3-P4 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15623
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             185     IN      A       216.58.221.46

;; Query time: 2 msec
;; SERVER: 172.16.0.1#53(172.16.0.1)
;; WHEN: Fri Apr 13 13:12:08 India Standard Time 2018
;; MSG SIZE  rcvd: 55

PS D:\Users\shant> dig example.com `@1.1.1.1

; <<>> DiG 9.10.3-P4 <<>> example.com @1.1.1.1
;; global options: +cmd
;; connection timed out; no servers could be reached
PS D:\Users\shant> dig example.com `@1.0.0.1

; <<>> DiG 9.10.3-P4 <<>> example.com @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29750
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;example.com.                   IN      A

;; ANSWER SECTION:
example.com.            626     IN      A       93.184.216.34

;; Query time: 51 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Fri Apr 13 13:12:58 India Standard Time 2018
;; MSG SIZE  rcvd: 56

PS D:\Users\shant> dig example.com `@8.8.8.8

; <<>> DiG 9.10.3-P4 <<>> example.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25166
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;example.com.                   IN      A

;; ANSWER SECTION:
example.com.            21307   IN      A       93.184.216.34

;; Query time: 102 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Apr 13 13:13:20 India Standard Time 2018
;; MSG SIZE  rcvd: 56

PS D:\Users\shant> dig +short CHAOS TXT id.server `@1.1.1.1
;; connection timed out; no servers could be reached
PS D:\Users\shant> dig +short CHAOS TXT id.server `@1.0.0.1
"sin02"
PS D:\Users\shant> dig `@ns3.cloudflare.com whoami.cloudflare.com txt +short
"125.99.163.xxx"
PS D:\Users\shant> tracert 1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.16.0.1
  2     8 ms     7 ms     8 ms  10.111.0.1
  3    10 ms     9 ms     8 ms  125.99.170.9
  4     9 ms    21 ms     8 ms  1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

Trace complete.
PS D:\Users\shant> tracert 1.0.0.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  172.16.0.1
  2     8 ms     8 ms     8 ms  10.111.0.1
  3     8 ms     7 ms     8 ms  125.99.170.9
  4    10 ms     9 ms     8 ms  125.99.170.1
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    81 ms    79 ms    81 ms  1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]

Trace complete.
PS D:\Users\shant> dig +tcp `@1.1.1.1 id.server CH TXT
;; Connection to 1.1.1.1#53(1.1.1.1) for id.server failed: connection refused.
PS D:\Users\shant> dig +tcp `@1.0.0.1 id.server CH TXT

; <<>> DiG 9.10.3-P4 <<>> +tcp @1.0.0.1 id.server CH TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17762
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;id.server.                     CH      TXT

;; ANSWER SECTION:
id.server.              0       CH      TXT     "maa01"

;; Query time: 59 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Fri Apr 13 13:22:34 India Standard Time 2018
;; MSG SIZE  rcvd: 56

I have raised an issue with ISP, but I doubt its gonna be useful until CF helps them out.

Thanks.

UPDATE: Port 22 appears to be open on 1.1.1.1 (which ever server/router that is)


1.1.1.1 is not working with Hathway Broadband (Indian ISP)
#2

Thanks for the report! If something is listening on port 22 it isn’t Cloudflare. Can you please provide us some additional troubleshooting information, so we can try to narrow down the issue?


#3

All of that is in the expandable section “Summary”.

If you need anything else, let me know.


#4

Your traceroute for 1.1.1.1 didn’t go that far. It’s probably somewhere in your ISPs network. @cscharff

PS D:\Users\shant> tracert 1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.0.1
2 8 ms 7 ms 8 ms 10.111.0.1
3 10 ms 9 ms 8 ms 125.99.170.9
4 9 ms 21 ms 8 ms 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]

Trace complete.


#5

Ah thanks missed that :facepalm:

I’ll pass along to our networking team. Thank you!


#6

Yup, that is my first guess. The abuse of 1.1.1.1 in switches. I have a pending service request with the ISP, which I’ll update here “if” they decide to take action.