DNS queries can be done by two protocols TCP UDP, DNS tested by the dig command parsing
- udp way, the first response packet is treated as valid data
- tcp way, sometimes effective, it may be rest
- Data will be modified in two ways, because we are in the LAN
Use dig resolve domain names
dig accounts.google.co.jp @1.1.1.1 +short
74.86.118.24
This shows that the results are wrong, add +tcp
parameters to try again
kasumi@kasumi:~$ dig accounts.google.co.jp @1.1.1.1 +short +tcp
accounts-cctld.l.google.com.
172.217.164.99
Now the results of analytical and abroad, as barely a
d@MyServer: ~ $ dig @1.1.1.1 accounts.google.co.jp +short
accounts-cctld.l.google.com.
172.217.164.99
d@MyServer: ~ $ curl cip.cc/216.58.194.195
IP : 216.58.194.195
地址 : GOOGLE.COM GOOGLE.COM
数据二 : 美国 | 加利福尼亚州圣克拉拉县山景市谷歌公司
数据三 : 美国加利福尼亚旧金山 | 谷歌
URL : http://www.cip.cc/216.58.194.195
How to solve the DNS Pollution problem?
END