Why the dns 1.0.0.1 is faster than 1.1.1.1 for me?

Zero Trust 1.1.1.1
, ,
1

Why is DNS 1.0.0.1 faster than 1.1.1.1 for me? Why does 1.0.0.1 work better than 1.1.1.1 in response times? Is there a problem that this happens?

2

They should be almost the same. How are you testing this?

Here are some troubleshooting tips:

3
4

The ‘dig’ commands in that article will show you the response time for each query.

‘traceroute’ is handy for overall connectivity performance to each address.

‘dig’ is the more useful of the two when testing real-world performance.

5

Observed the same sustainable behavior when configured DNS on a host in Russia.
1.0.0.1 is about 10 times faster than 1.1.1.1 - 3 vs. 40 ms

$ dig CHAOS TXT id.server @1.1.1.1

; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> CHAOS TXT id.server @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27521
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

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

;; Query time: 40 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Oct 01 13:42:23 MSK 2018
;; MSG SIZE  rcvd: 54

$ dig CHAOS TXT id.server @1.0.0.1

; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> CHAOS TXT id.server @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60396
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

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

;; Query time: 3 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Oct 01 13:43:36 MSK 2018
;; MSG SIZE  rcvd: 54
6

Can you post traceroutes to both addresses?

7

It seems the address in question is misrouted out of the country.

$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  xxxxxxxxxxxxxxxxxxxxxxxxxxx
 2  * * *
 3  * * *
 4  87.226.221.64 (87.226.221.64)  3.873 ms  3.756 ms  3.798 ms
 5  213.59.211.63 (213.59.211.63)  3.042 ms 213.59.211.255 (213.59.211.255)  2.956 ms 213.59.212.235 (213.59.212.235)  2.958 ms
 6  rostelecom-ic-319651-ffm-b1.c.telia.net (62.115.151.97)  38.960 ms  38.820 ms  38.727 ms
 7  ffm-b1-link.telia.net (62.115.151.96)  39.403 ms  54.288 ms  54.222 ms
 8  Cloudflare-ic-328337-ffm-b1.c.telia.net (62.115.144.199)  44.247 ms  44.212 ms  44.115 ms
 9  one.one.one.one (1.1.1.1)  50.002 ms  47.004 ms  46.858 ms

$ traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
 1  xxxxxxxxxxxxxxxxxxxxxxxxxxx
 2  xxxxxxxxxxxxxxxxxxxxxxxxxxx
 3  77.37.250.202 (77.37.250.202)  2.082 ms  2.192 ms  2.293 ms
 4  msk-ix.Cloudflare.com (195.208.209.7)  5.727 ms  5.641 ms  9.625 ms
 5  one.one.one.one (1.0.0.1)  3.027 ms  2.955 ms  2.937 ms
8

@cloonan @cs-cf @ryan

9

@irtefa I noticed you reacted to some similar issues, maybe you can take a look on this one as well?

1 Like
10

Our team is looking into this.

1 Like
11

What are the source IPs for the hosts whens you are performing the traceroute? Or, are you using the same host?

12

yes, that was the same host in AS42610

Here is another example with another large ISP in Russia. Looking glass service was used to compare routes to 1.1.1.1 and 1.0.0.1, “Node” was set to “AS3216 Moscow”:

Tracing the route to 1.1.1.1

1 p4.Moscow.gldn.net (79.104.225.73) 5 msec 11 msec 1 msec
2 p2.Moscow.gldn.net (79.104.227.255) 19 msec
p1.Moscow.gldn.net (79.104.226.255) 1 msec 0 msec
3 pe05.KK12.Moscow.gldn.net (79.104.225.15) 2 msec
pe05.KK12.Moscow.gldn.net (79.104.225.13) 2 msec
pe05.KK12.Moscow.gldn.net (79.104.225.15) 0 msec
4 be10.tf01-02.Moscow.gldn.net (81.211.45.63) 1 msec 1 msec 1 msec
5 EDN-SOVINTE.ear2.Stockholm2.Level3.net (213.249.107.10) 42 msec 42 msec 43 msec
6 *
195.89.97.213 41 msec 41 msec
7 ae2-xcr1.fix.cw.net (195.2.9.238) 41 msec 37 msec 42 msec
8 ix-ae-26-0.tcore1.fr0-frankfurt.as6453.net (195.219.50.101) 44 msec 42 msec 44 msec
9 if-ae-6-2.thar1.f2c-frankfurt.as6453.net (195.219.50.174) 42 msec
s-b5-link.telia.net (62.115.141.199) 45 msec
s-b5-link.telia.net (62.115.133.25) 43 msec
10 Cloudflare-ic-322350-s-b5.c.telia.net (62.115.35.155) 43 msec
195.219.148.122 56 msec
Cloudflare-ic-322350-s-b5.c.telia.net (62.115.35.155) 43 msec
11 one.one.one.one (1.1.1.1) 45 msec 46 msec 44 msec

Tracing the route to 1.0.0.1

1 p4.Moscow.gldn.net (79.104.225.73) 18 msec 33 msec
p3.Moscow.gldn.net (79.104.225.69) 7 msec
2 mx01.Stockholm.gldn.net (79.104.225.6) 18 msec
mx01.Stockholm.gldn.net (79.104.225.38) 18 msec 19 msec
3 * * *
4 one.one.one.one (1.0.0.1) 41 msec 41 msec 41 msec

13

Looks much better now:

image
image497×622 45.8 KB

image
image385×532 41.8 KB

Still a shorter path to 1.0.0.1 though.

14