腾讯 DNSPod DNS 119.29.29.29 为什么不能解析 www. PHP .net

V2EX = way to explore

V2EX 是一个关于分享和探索的地方

现在注册

已注册用户请登录

工单节点使用指南

请用平和的语言准确描述你所遇到的问题

厂商的技术支持和你一样也是有喜怒哀乐的普通人类，尊重是相互的

如果是关于 V2EX 本身的问题反馈，请使用反馈节点

刚开始还怀疑是我的网络问题, 搜索了半天找到一个在线测试的工具

http://tool.chinaz.com/dns/?type=1&host=www.php.net&ip=119.29.29.29

22 条回复 2017-07-26 14:34:33 +08:00

gclove

2017-07-25 14:03:49 +08:00

先问问 V 友, 现在哪个 DNS 稳定可靠吖 ?
114.114.114.114 我都觉得不靠谱, 记得大学充值游戏点卡时解析也有问题
后来用过 223.5.5.5, 只有有段时间感觉解析和 ping 都比较慢, 我就换成 119.29.29.29 了

暂时我打算用回 223.5.5.5 了

xfspace

2017-07-25 14:13:49 +08:00 via Android

1.2.4.8

Ellison

2017-07-25 14:20:56 +08:00

我这也是 119.29.29.29 时不时就会抽

goldenalex

2017-07-25 14:26:05 +08:00

不是 1.1.1.1 2.2.2.2 4.4.4.4 8.8.8.8 比较好么?

xbonline

2017-07-25 14:28:08 +08:00

目前已用回运营商分配的。杭州电信，暂时没发现劫持，没跳 114

suikator

2017-07-25 14:31:46 +08:00 via Android

dig www.php.net @119.29.29.29 +tcp
就行不是很懂你们 119

pqee

2017-07-25 14:35:10 +08:00

~ nslookup php.net 119.29.29.29
Server: 119.29.29.29
Address: 119.29.29.29#53

Non-authoritative answer:
Name: php.net
Address: 72.52.91.14

~ nslookup www.php.net 119.29.29.29
Server: 119.29.29.29
Address: 119.29.29.29#53

Non-authoritative answer:
*** Can't find www.php.net: No answer

pqee

2017-07-25 14:35:19 +08:00

确实是这个情况

bubuyu

2017-07-25 14:43:34 +08:00

刚刚试了下，119.29.29.29 竟然只解出 ipv6 的地址...
> www.php.net
服务器: pdns.dnspod.cn
Address: 119.29.29.29

名称: www.php.net
Address: 2a02:cb41::7

Showfom

PRO

2017-07-25 14:43:45 +08:00

啊

C:\Users\David>nslookup qq.com 119.29.29.29
Server: pdns.dnspod.cn
Address: 119.29.29.29

Non-authoritative answer:
Name: qq.com
Addresses: 61.135.157.156
125.39.240.113

C:\Users\David>nslookup php.net 119.29.29.29
Server: pdns.dnspod.cn
Address: 119.29.29.29

Non-authoritative answer:
Name: php.net
Addresses: 2a02:cb41::7
72.52.91.14

C:\Users\David>nslookup www.php.net 119.29.29.29
Server: pdns.dnspod.cn
Address: 119.29.29.29

Non-authoritative answer:
Name: www.php.net
Addresses: 2a02:cb41::7
220.181.136.30
220.181.136.41
72.52.91.14

xiaoz

2017-07-25 14:53:34 +08:00

我这里解析正常：
dig @119.29.29.29 www.php.net

; <<>> DiG 9.9.9-P5 <<>> @119.29.29.29 www.php.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16925
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.php.net. IN A

;; ANSWER SECTION:
www.php.net. 300 IN A 220.181.136.41
www.php.net. 300 IN A 72.52.91.14
www.php.net. 300 IN A 220.181.136.30

; Query time: 947 msec
;; SERVER: 119.29.29.29#53(119.29.29.29)
;; WHEN: Tue Jul 25 14:52:23 ?D1ú±ê×?ê±?? 2017
;; MSG SIZE rcvd: 88

w910621

2017-07-25 14:57:42 +08:00

这边移动 114DNS 阿里 DNS 全部屏蔽唯独 119 没事估计太小众了

openbaby

2017-07-25 15:12:37 +08:00

移动宽带，在用 oneDNS，解析一切正常。
我这里 119.29.29.29 自从上次被攻击后，就一直没法解析了，dig 任何域名都无响应。。。

yatesun

2017-07-25 16:34:55 +08:00

应该多个 dns 同时查询，去最快并且有数据的结果

yatesun

2017-07-25 16:35:18 +08:00

然后再也没有遇到问题

run2

2017-07-25 16:48:50 +08:00

~ nslookup www.php.net 119.29.29.29
Server: 119.29.29.29
Address: 119.29.29.29#53

Non-authoritative answer:
Name: www.php.net
Address: 220.181.136.41
Name: www.php.net
Address: 72.52.91.14
Name: www.php.net
Address: 220.181.136.30

~ dig @119.29.29.29 www.php.net

; <<>> DiG 9.9.7-P3 <<>> @119.29.29.29 www.php.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8164
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.php.net. IN A

;; ANSWER SECTION:
www.php.net. 270 IN A 220.181.136.30
www.php.net. 270 IN A 72.52.91.14
www.php.net. 270 IN A 220.181.136.41

;; Query time: 73 msec
;; SERVER: 119.29.29.29#53(119.29.29.29)
;; WHEN: Tue Jul 25 16:47:15 CST 2017
;; MSG SIZE rcvd: 88

skylancer

2017-07-25 16:55:13 +08:00

深圳天威经常 SRVFAIL，完全没想用 DNSPod 的想法

gclove

2017-07-25 18:29:24 +08:00

@xiaoz @Showfom @suikator 我这边不加 tcp 不行, 加了可以

参考 http://tool.chinaz.com/dns/?type=1&host=www.php.net&ip=119.29.29.29

nslookup www.php.net 119.29.29.29
Server: 119.29.29.29
Address: 119.29.29.29#53

Non-authoritative answer:
*** Can't find www.php.net: No answer

wwqgtxx

2017-07-26 08:02:17 +08:00

南通电信，也要加 TCP 才有结果

D:\BIND9.10.5-P1.x64>dig @119.29.29.29 www.php.net

; <<>> DiG 9.10.5-P1 <<>> @119.29.29.29 www.php.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26202
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.php.net. IN A

;; Query time: 17 msec
;; SERVER: 119.29.29.29#53(119.29.29.29)
;; WHEN: Wed Jul 26 08:01:04 ?D1ú±ê×?ê±?? 2017
;; MSG SIZE rcvd: 40

D:\BIND9.10.5-P1.x64>dig +tcp @119.29.29.29 www.php.net

; <<>> DiG 9.10.5-P1 <<>> +tcp @119.29.29.29 www.php.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8642
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.php.net. IN A

;; ANSWER SECTION:
www.php.net. 300 IN A 220.181.136.30
www.php.net. 300 IN A 220.181.136.41
www.php.net. 300 IN A 220.181.136.55

;; Query time: 439 msec
;; SERVER: 119.29.29.29#53(119.29.29.29)
;; WHEN: Wed Jul 26 08:01:49 ?D1ú±ê×?ê±?? 2017
;; MSG SIZE rcvd: 88

lslqtz

2017-07-26 09:13:25 +08:00

同不行
C:\Users\lslqtz>dig www.php.net

; <<>> DiG 9.10-P2 <<>> www.php.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40300
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.php.net. IN A

;; Query time: 21 msec
;; SERVER: 119.29.29.29#53(119.29.29.29)
;; WHEN: Wed Jul 26 09:13:02 中国标准时间 2017
;; MSG SIZE rcvd: 40

lslqtz

2017-07-26 09:14:02 +08:00

+tcp 同可以

kkk123

2017-07-26 14:34:33 +08:00

试了几次, 50%失败几率.
$ dig www.php.net @119.29.29.29 +tcp
;; communications error to 119.29.29.29#53: end of file