Results are fiddled with in Thailand?

DNS & Network
#1

GOOGLE

dig cock.li @8.8.8.8

; <<>> DiG 9.16.8-Ubuntu <<>> cock.li @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64117
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
cock.li.		164	IN	A	193.239.85.202

;; Query time: 32 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Oct 09 23:48:43 +07 2021
;; MSG SIZE  rcvd: 52

CLoudflare

dig cock.li @1.1.1.1

; <<>> DiG 9.16.8-Ubuntu <<>> cock.li @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 45860
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority)
;; QUESTION SECTION:
;cock.li.			IN	A

;; Query time: 3984 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat Oct 09 23:49:55 +07 2021
;; MSG SIZE  rcvd: 42

Wondering if Thailand is intercepting/censoring traffic? (given the high latencies)

mtr 1.1.1.1 --report
Start: 2021-10-09T23:50:48+0700
HOST: i                           Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- _gateway                   0.0%    10    3.7   3.7   3.5   4.0   0.2
  2.|-- 192.168.1.1                0.0%    10    7.5   5.0   3.5  12.6   2.9
  3.|-- 172.16.3.1                 0.0%    10    6.8   6.7   4.3   7.3   0.9
  4.|-- 103.206.205.254            0.0%    10    6.8   7.5   5.7  10.9   1.7
  5.|-- 103.247.63.228             0.0%    10    7.0   7.7   6.8  13.7   2.1
  6.|-- 32.178.82.58.nix.jastel.c  0.0%    10   52.8  20.6   6.9  89.2  28.0
  7.|-- 18.85.50.182.static-corp.  0.0%    10    6.3   8.0   6.3  13.1   2.5
  8.|-- 93.85.50.182.static-corp.  0.0%    10    7.2   7.5   4.7  10.5   1.8
  9.|-- 10.33.33.174              80.0%    10    7.1   7.3   7.1   7.4   0.3
 10.|-- 39.85.50.182.static-corp.  0.0%    10    6.8  17.2   6.1  94.9  27.7
 11.|-- one.one.one.one            0.0%    10    7.2   8.0   4.4  18.8   3.9
#2

It could be but I doubt the DNS filter would cause the high latency - at least if it’s implemented properly. Could you try querying another domain and observing whether the latency is the same?

1.1.1.1 resolves both of those domains without issues on my end.

[[email protected] ~]$ dig cock.li @1.1.1.1

; <<>> DiG 9.16.21 <<>> cock.li @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20204
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;cock.li.                       IN      A

;; ANSWER SECTION:
cock.li.                273     IN      A       193.239.85.202

;; Query time: 13 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat Oct 09 18:54:30 CEST 2021
;; MSG SIZE  rcvd: 52

[[email protected] ~]$ dig vc.gg @1.1.1.1

; <<>> DiG 9.16.21 <<>> vc.gg @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41811
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;vc.gg.                         IN      A

;; ANSWER SECTION:
vc.gg.                  261     IN      A       185.100.85.212

;; Query time: 13 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat Oct 09 18:54:57 CEST 2021
;; MSG SIZE  rcvd: 50
#3

Other domains are perfectly fine

dig example.com @1.1.1.1

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

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

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

;; Query time: 7 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Oct 10 01:23:15 +07 2021
;; MSG SIZE  rcvd: 56


dig google.com @1.1.1.1

; <<>> DiG 9.16.8-Ubuntu <<>> google.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3825
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
google.com.		94	IN	A	172.217.166.142

;; Query time: 7 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Oct 10 01:23:40 +07 2021
;; MSG SIZE  rcvd: 55


dig nytimes.com @1.1.1.1

; <<>> DiG 9.16.8-Ubuntu <<>> nytimes.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41109
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
nytimes.com.		85	IN	A	151.101.129.164
nytimes.com.		85	IN	A	151.101.1.164
nytimes.com.		85	IN	A	151.101.65.164
nytimes.com.		85	IN	A	151.101.193.164

;; Query time: 31 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sun Oct 10 01:24:18 +07 2021
;; MSG SIZE  rcvd: 104