.top 后缀的域名使用 8.8.8.8 无法进行解析

DNS 参考资料

› dnslib for Python

This topic created in 2896 days ago, the information mentioned may be changed or developed.

.top 后缀的域名使用 8.8.8.8 无法进行解析。

; <<>> DiG 9.10.8 <<>> baidu.top @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 3359
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 52 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Dec 03 11:34:41 CST 2018
;; MSG SIZE  rcvd: 38

; <<>> DiG 9.10.8 <<>> qq.top @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 46709
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 51 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Dec 03 11:36:46 CST 2018
;; MSG SIZE  rcvd: 35

23 replies • 2019-03-09 13:48:04 +08:00

leido

Dec 3, 2018 via Android

这个域名 ns 服务器在国外，估计楼主网不通 8.8.8.8

leido

Dec 3, 2018 via Android

qq.top 没有这个域名

lhx2008

Dec 3, 2018

是可以复现，但是这个 8.8.8.8 真不真就不知道了

lhx2008

Dec 3, 2018

楼主可以看下 https://tools.ipip.net/dns.php 的结果，大部分外国节点还是可以解析到的，国内 Ip 大部分解析不到

leavic

Dec 3, 2018

; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> baidu.top @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41662
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
baidu.top. 299 IN A 137.74.127.233

;; Query time: 92 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Dec 03 04:48:12 UTC 2018
;; MSG SIZE rcvd: 54

===========
DNS 劫持了解一下？

kimi815

Dec 3, 2018

```
; <<>> DiG 9.10.8 <<>> sina.top @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 1177
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 54 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Dec 03 12:52:20 CST 2018
;; MSG SIZE rcvd: 37
```

dianso

Dec 3, 2018

一会我去给配齐说一声吧

zbinlin

Dec 3, 2018

.top 是国内公司注册的，8.8.8.8 解析不到也不奇怪

songkl

Dec 3, 2018

为啥我就成功了呢？

; <<>> DiG 9.10.6 <<>> @8.8.8.8 baidu.top
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14171
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
baidu.top. 300 IN A 137.74.127.233

;; Query time: 69 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Dec 03 16:07:09 CST 2018
;; MSG SIZE rcvd: 54

holajamc

Dec 3, 2018

为什么不考虑一下 DNS 劫持？
; <<>> DiG 9.10.3-P4-Debian <<>> baidu.top @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13740
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

;; Query time: 16 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Dec 03 16:14:10 HKT 2018
;; MSG SIZE rcvd: 38

boris1993

Dec 3, 2018 via Android

楼主如果用国内的网，那么四个 8 是假冒的

bin456789

Dec 3, 2018

@lhx2008 在这个网页指定 8.8.8.8 解析
亚太区域会解析不了，例如日本、新加坡
不止.top 后缀 .wang 后缀也是
/t/512276，前几天我发帖还被人喷

fengxing

Dec 3, 2018

dig +trace 看看是不是被劫持了就知道了

syuraking

Dec 3, 2018

表示，我的 JP+SG，用 4 个 8 解析毫无问题

kimi815

Dec 3, 2018

我是在印度的机器上测试的

xfspace

Dec 4, 2018 via Android

; <<>> DiG 9.11.5-1-Debian <<>> baidu.top @8.8.8.8 +trace
;; global options: +cmd
. 91825 IN NS m.root-servers.net.
. 91825 IN NS b.root-servers.net.
. 91825 IN NS c.root-servers.net.
. 91825 IN NS d.root-servers.net.
. 91825 IN NS e.root-servers.net.
. 91825 IN NS f.root-servers.net.
. 91825 IN NS g.root-servers.net.
. 91825 IN NS h.root-servers.net.
. 91825 IN NS i.root-servers.net.
. 91825 IN NS a.root-servers.net.
. 91825 IN NS j.root-servers.net.
. 91825 IN NS k.root-servers.net.
. 91825 IN NS l.root-servers.net.
. 91825 IN RRSIG NS 8 0 518400 20181214050000 20181201040000 2134 . WzCdFNzl1x6/FUis3EIRHj6pu20SaFpDIjQFPm3R84aVLFd63fwsv3Zo 9EVMJuwIDuhbF7tSxesd4xdfLiQK2sAnMZBx/+UwD2pvooCPfygBE0Y/ VnD4ZZCyREKNbNdw4r0kZ/s144t3wEx2FiGV69HSDgjA1BB49h/TL+Ts E7ss6e1hLUdc+K1YgI6T6W+MbAamZ+EPTpADMDjZb8YHckzb01eZw9ur BcHh564vzkpqPZUFnwX8XJATUI+/Zs2sR9hI8bdetPnp6c1lW16ySUYo ZEqV8DJZrKxIg8gzmGDD5PVGnq5s828/ZxLe/EtwMWBNDriy+bcoI6jY 2fv28w==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 27 ms

top. 172800 IN NS a.zdnscloud.com.
top. 172800 IN NS b.zdnscloud.com.
top. 172800 IN NS c.zdnscloud.com.
top. 172800 IN NS d.zdnscloud.com.
top. 172800 IN NS f.zdnscloud.com.
top. 172800 IN NS g.zdnscloud.com.
top. 172800 IN NS i.zdnscloud.com.
top. 172800 IN NS j.zdnscloud.com.
top. 86400 IN DS 18451 8 2 3F5E192F020D6F90C69EC3B46EBB725447ACD57A38CBEDA9B9B6B765 883B90D5
top. 86400 IN RRSIG DS 8 1 86400 20181216140000 20181203130000 2134 . xbeJggJXRCBBr4XXViP4cCJPYJRWf4DVCBD0DfBPWR7X9iTRd+V9+tej UTU3zxat0P5a9dIRl4U9sTN/OreOERCfP8ep5mZBhNCZkbJQyJinANJL A7dydsVNDrpTvRC8AFUzoRHMexV+c0CWPPpaPuhSdoz4ECcin0TpoBzr cgVi1ZVYXqhF+ODHQ02Ut8ejgppcCK1e61gqrtdpB00/+SocBTTrHMWv tcqLtBEa0R7Qon5KCGlmKit+M6qEtZ3aLwCx2EvXE8cTOqAqYu7Y0p9y xxwCmXZ0Xbvf7I6Mm1/xRsWjOQI4AGMqC5AnhbJ6soKLKsN6kPGdalw2 MXV65g==
couldn't get address for 'j.zdnscloud.com': not found
;; Received 666 bytes from 192.203.230.10#53(e.root-servers.net) in 197 ms

baidu.top. 3600 IN NS ns5.brandshelter.us.
baidu.top. 3600 IN NS ns4.brandshelter.net.
baidu.top. 3600 IN NS ns2.brandshelter.de.
baidu.top. 3600 IN NS ns3.brandshelter.info.
baidu.top. 3600 IN NS ns1.brandshelter.com.
2jqv8t5hd28bqpv5badv3j75107hq9s3.top. 3600 IN NSEC3 1 0 5 3A1B91E364D39AEB 2JR0H59F7J2I9MGVTQTC38U8L5U467T9 NS
2jqv8t5hd28bqpv5badv3j75107hq9s3.top. 3600 IN RRSIG NSEC3 8 2 3600 20181207124543 20181123050227 3976 top. WtHqv+LdQAH5MW2jl8NnJ72JCspne0upfNOSL+VklX/93Fmq79CO+KuN Vk1gxhLo9/uCIMPnWe7FJ8rXQGCYNnVbqIj2Eqmv+wJHbXefvCZOWfE1 8z8WUCWMJqreIYW32xfSBq5oeBTTxyXOu5MlLRUqdYOeX0YhHsiB7YvZ KZ4=
;; Received 480 bytes from 203.99.24.1#53(a.zdnscloud.com) in 50 ms

递归轮询到了 i j 的 NS 有 problem
top. 172800 IN NS i.zdnscloud.com.
top. 172800 IN NS j.zdnscloud.com.

这 2 台被 remove 注册局不 update [dot]TOP 的 NS
轮询其余的 NS 毛问题
8.8.8.8 no problem

LanFomalhaut

Dec 4, 2018

@xfspace 这个 i 跟 J 只有 AAAA 记录木有 A 记录 23333

xinxuyue

Dec 21, 2018 via Android

目测阿里云受害者

kisara

Feb 24, 2019

为啥要用这种莫名其妙的后缀？

hhhsuan

Mar 9, 2019

@kisara #19 因为比较酷啊

kisara

Mar 9, 2019

@hhhsuan 我最不喜欢 New gTLD 的原因就是好多人看不出来这是个网址连很多搞 cs 都不知道 .com 结尾的话所有人一眼就知道这是网址。。

hhhsuan

Mar 9, 2019

@kisara #21 这样才酷啊，有小圈子的感觉。如果一个东西连圈外的人都知道了，那还有什么酷劲

kisara

Mar 9, 2019

@hhhsuan 给人一种非常不专业的感觉啊。。。看过很多教授、大佬的主页基本都是 .com / .org 基本没见过用 New gTLD 的写博客展示个性的话应该还好吧