aa65535 / openwrt-chinadns Goto Github PK

View Code? Open in Web Editor NEW

707.0 65.0 180.0 122 KB

ChinaDNS for OpenWrt/LEDE

License: GNU General Public License v3.0

Makefile 54.83% Shell 45.17%

openwrt chinadns lede

openwrt-chinadns's People

Contributors

Stargazers

Watchers

Forkers

berry10086 hedongjie linfang26 znanl kkkgo jhbsz yaksa-me qurikuduo sugarinmyheart alee1211 dodohappi malenie oldboy-chen mveplus dbalee unzqxg braveguywallce xyb digisonny daqingguo l4nneret blog2i2j wang20150419 minfu relaxy jn7163 telchina md11235 shindo10 ghostry janbobo 66ccff q158073378252010 lincank heistrock alanljj royalwang zshchou llliqqq changeyourname jermingfan noscripter earthgavinlee evilperfect ciqdj popoimm harmy huangya90 kkrrll joecool2046 xuan84 iamaxisme tksmai moecao evalevil fourleaves connlan rinex20 genemill jiepan jackylinpda joe-server ctw8989 yibin0083 luckystarry huxiangyu wangyx0055 mapleshadow everthis mdp19900707 billxq forging2012 xianping016 jibenfa willame liyvhg liangyuan64 xiaobingjian jack338c tong2018 hlxyb icodex v2r0 cathywife u20024804 zheng-song peterwillcn zr0621 cugbcm sevenliao77 ajuan2005 chobitsos fqtools koho mmd1989 silent-x newlifes01 banaoa xkxf1293 mickey50

openwrt-chinadns's Issues

请问如何反馈被墙网址

如瘾科技国外中文版 http://chinese.engadget.com/ 无法打开网页，或打开网页不完整
我不知道该去哪里反馈只好在这里发帖了…… :)

chinadns在cc15.05一直不能运行，不知道什么问题，help me

加了-m，chinadns取了国内ip结果
去掉，有delay后，chinadns采用了国外的结果。
现在 @aa65535 你的luci-app里面已经没了-m的开关了，默认是打开的。之前我用了gwflist生成的dnsmasq规则，本来就没有这个问题，不过昨天重刷路由发现了。目前继续将dnsmasq规则添上去解决。另一种方式是把init.d里面的-m去了，不过相信不少人还是不大会改的吧，好多人都是看着别人写的步骤依葫芦画瓢来的。

dig @192.168.1.1 -p 35352 www.google.com

root@OpenWrt:/tmp# chinadns -c /etc/ignore.list -b 0.0.0.0 -p 35352 -v -s 211.138.24.66,127.0.0.1:5311
Fri Sep  4 02:50:54 2015 request www.google.com
Fri Sep  4 02:50:54 2015 response www.google.com from 211.138.24.66:53 - 211.138.21.142, delay
Fri Sep  4 02:50:54 2015 response www.google.com from 127.0.0.1:5311 - 216.58.221.132, delay

root@OpenWrt:/tmp# chinadns -c /etc/ignore.list -b 0.0.0.0 -p 35352 -m -v -s 211.138.24.66,127.0.0.1:5311
Fri Sep  4 02:52:00 2015 request www.google.com
Fri Sep  4 02:52:00 2015 response www.google.com from 211.138.24.66:53 - 211.138.21.142, pass
Fri Sep  4 02:52:00 2015 response www.google.com from 127.0.0.1:5311 - 216.58.221.132, pass

如上所示加了-m时候国内dns结果是pass

这情况不知道好解决不。
PS：clowwindy现在这状况的情况下，chinadns还有人维护么？

编译错误

PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)/$(PKG_NAME)-$(PKG_VERSION)
是不是应该修改为
PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)/openwrt-chinadns-$(PKG_VERSION)
？
不过修改了我这里依然编译失败

运行一段时间后失效，查看日志只有request没有response

——————————————————————————————————
2016.01.13
——————————————————————————————————
今天发现的问题是，国外dns解析服务器无反应，只有国内的有反应。
怀疑是被GFW过滤掉了？
211.137.191.26是本地isp的dns
日志：
Wed Jan 13 08:11:11 2016 request live.github.com from 211.137.191.26:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Wed Jan 13 08:11:11 2016 response live.github.com from 211.137.191.26:53 - 192.30.252.91, filter
Wed Jan 13 08:11:11 2016 response live.github.com from 211.137.191.26:53 - 192.30.252.91, filter
Wed Jan 13 08:11:15 2016 request live.github.com from 211.137.191.26:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Wed Jan 13 08:11:15 2016 response live.github.com from 211.137.191.26:53 - 192.30.252.91, filter
Wed Jan 13 08:11:15 2016 response live.github.com from 211.137.191.26:53 - 192.30.252.89, filter

dig 8.8.8.8 也毫无反应
DIG：
root@OpenWrt:~# dig @8.8.8.8 www.baidu.com

; <<>> DiG 9.9.4 <<>> @8.8.8.8 www.baidu.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

国内dns解析有反应
root@OpenWrt:~# dig @211.137.191.26 www.baidu.com

; <<>> DiG 9.9.4 <<>> @211.137.191.26 www.baidu.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24458
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 5, ADDITIONAL: 6

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

;; ANSWER SECTION:
www.baidu.com. 281 IN CNAME www.a.shifen.com.
www.a.shifen.com. 247 IN A 111.13.100.92
www.a.shifen.com. 247 IN A 111.13.100.91

;; AUTHORITY SECTION:
a.shifen.com. 87 IN NS ns5.a.shifen.com.
a.shifen.com. 87 IN NS ns4.a.shifen.com.
a.shifen.com. 87 IN NS ns3.a.shifen.com.
a.shifen.com. 87 IN NS ns1.a.shifen.com.
a.shifen.com. 87 IN NS ns2.a.shifen.com.

;; ADDITIONAL SECTION:
ns1.a.shifen.com. 175 IN A 61.135.165.224
ns2.a.shifen.com. 175 IN A 180.149.133.241
ns3.a.shifen.com. 175 IN A 61.135.162.215
ns4.a.shifen.com. 175 IN A 115.239.210.176
ns5.a.shifen.com. 175 IN A 119.75.222.17

;; Query time: 14 msec
;; SERVER: 211.137.191.26#53(211.137.191.26)
;; WHEN: Wed Jan 13 08:19:55 GMT 2016
;; MSG SIZE rcvd: 271

——————————————————————————————————
2016.01.12
——————————————————————————————————
Tue Jan 12 10:20:39 2016 request www.baidu.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:39 2016 request www.baidu.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:40 2016 request www.baidu.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:42 2016 request www.baidu.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:43 2016 request nexus.officeapps.live.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:43 2016 request nexus.officeapps.live.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:44 2016 request nexus.officeapps.live.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:44 2016 request imap.qq.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:44 2016 request docker-test.leancloud.cn from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:44 2016 request rtm53.leancloud.cn from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:46 2016 request nexus.officeapps.live.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:46 2016 request rm.api.weibo.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:46 2016 request rm.api.weibo.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:46 2016 request www.google.co.jp from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:46 2016 request www.google.co.jp from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
Tue Jan 12 10:20:46 2016 request www.baidu.com from 114.114.114.114:53 8.8.8.8:53 208.67.222.222:443 127.0.0.1:5151
如上日志，只有request没有response，重启路由器才能解决
其中127.0.0.1:5151 是我的ss
配置没有问题，因为之前稳定用了差不多1个月。

为什么有时候国外的IP都会向国内的dns服务器解析？

添加了/etc/opkg.conf 依然无法安装

硬件信息：OpenWrt Chaos Calmer 15.05 / LuCI 15.05-19-g488c5a7 Release (git-15.258.28302-30f6fe8)

按首页安装说明添加了src/gz openwrt_dist http://openwrt-dist.sourceforge.net/releases/ar71xx/packages
src/gz openwrt_dist_luci http://openwrt-dist.sourceforge.net/releases/luci/packages

之后执行

opkg update

提示

Downloading http://openwrt-dist.sourceforge.net/releases/ar71xx/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/openwrt_dist.
Downloading http://openwrt-dist.sourceforge.net/releases/ar71xx/packages/Packages.sig.
wget: server returned error: HTTP/1.1 404 Not Found
Signature check failed.
Remove wrong Signature file.
Downloading http://openwrt-dist.sourceforge.net/releases/luci/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/openwrt_dist_luci.
Downloading http://openwrt-dist.sourceforge.net/releases/luci/packages/Packages.sig.
wget: server returned error: HTTP/1.1 404 Not Found
Signature check failed.
Remove wrong Signature file.

继续执行opkg install ChinaDNS

提示

root@GL-AR150:~# opkg install ChinaDNS
Unknown package 'ChinaDNS'.
Collected errors:

opkg_install_cmd: Cannot install package ChinaDNS.
root@GL-AR150:~#

Renaming Upstream into ChinaDNS

The project will be renamed from ChinaDNS-C into ChinaDNS (Python version will be renamed into ChinaDNS-Python). I'm not sure if this will make big trouble(i.e. package name change, git repo url change, configuration key change, etc). If it is, I think we'd better just change the url, rather than the package name.

[Feature Request] 可否考虑在chinadns_chnroute.txt中加入对注释的支持？

http://www.v2ex.com/t/142145

因为购买了多台境外VPS，都可以直接从墙内访问，
所以需要把它们都加入到chinadns_chnroute.txt直接访问。
为了避免混乱，是否可以考虑在chinadns_chnroute.txt中加入对注释的支持？

或者提供一个生成包含主要VPS商机房IP段的chinadns_chnroute.txt的方法。

谢谢！

chinadns到底需要怎么设置？

被搞晕了。
更新到最新版，和luci最新版，从这下载更新的。

运行后，ps能看到：/usr/bin/chinadns -p 5353 -s 114.114.114.114,8.8.4.4 -c /etc/china_ip_list.txt -d -m

但是youtube域名就是解析不了。我kill掉进程，手工运行：
/usr/bin/chinadns -p 5353 -s 114.114.114.114,8.8.4.4 -c /etc/china_ip_list.txt -d -m -v

发现访问youtube.com，没有任何信息输出，我记得以前版本用-v参数可以看到实时的域名处理信息的。

chinadns除了在自己的luci界面上设置，还需要其他地方设置吗。
百度看了，有的人是设置到dhcp/dns的dns转发，地址写：127.0.0.0.1#5353 我也设置了，都没效果。

哎，真怎么就没有一个准确点的说明呢

Openwrt配置ChinaDNS疑问

在配置Openwrt使用ChinaDNS时，有两种方式：
1.本地服务器填写 127.0.0.1#5353
2.DNS转发填写 127.0.0.1#5353

请问这两种方式有什么区别？用哪种比较好？

使用一段时间后只有国内 DNS 在工作

版本：ChinaDNS_1.3.1-1_ramips_24kec.ipk
设置 DNS 为 114.114.114.114 和 ss 转发的 127.0.0.1:5353，无论是开启延时还是压缩，大概 2-3 分钟后，日志里就只剩下 114 在活跃，127 在日志里完全看不到，境外域名无法解析。重启 chinadns 就好了。

自动安装脚本没有更新

自动安装脚本http://openwrt-dist.sourceforge.net/auto_install.sh没有更新，还是ChinaDNS-C而不是ChinaDNS。

编译时缺少依赖库（这关闭的也太快了，唉，这真的是有问题啊！）

Package ChinaDNS is missing dependencies for the following libraries:
libc.so
libgcc_s.so.1

版本为1月10日trunk版

编译报错，附上日志！！

chinadns报错！！！！

checking whether the C compiler works... no
configure: error: in `/home/lo/OpenWrt-SDK-15.05.1/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/ChinaDNS/ChinaDNS-1.3.2':
configure: error: C compiler cannot create executables
See `config.log' for more details
Makefile:58: recipe for target '/home/lo/OpenWrt-SDK-15.05.1/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/ChinaDNS/ChinaDNS-1.3.2/.configured_yyn' failed
make[3]: *** [/home/lo/OpenWrt-SDK-15.05.1/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/ChinaDNS/ChinaDNS-1.3.2/.configured_yyn] Error 77
make[3]: Leaving directory '/home/lo/OpenWrt-SDK-15.05.1/package/chinadns'
package/Makefile:191: recipe for target 'package/chinadns/compile' failed
make[2]: *** [package/chinadns/compile] Error 2
make[2]: Leaving directory '/home/lo/OpenWrt-SDK-15.05.1'
package/Makefile:188: recipe for target '/home/lo/OpenWrt-SDK-15.05.1/staging_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/stamp/.package_compile' failed
make[1]: *** [/home/lo/OpenWrt-SDK-15.05.1/staging_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/stamp/.package_compile] Error 2
make[1]: Leaving directory '/home/lo/OpenWrt-SDK-15.05.1'
/home/lo/OpenWrt-SDK-15.05.1/include/toplevel.mk:174: recipe for target 'world' failed
make: *** [world] Error 2



shadowsocks-libev也报错了！！

configure: error: C compiler cannot create executables
See `config.log' for more details
Makefile:109: recipe for target '/home/lo/OpenWrt-SDK-15.05.1/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/shadowsocks-libev/openssl/shadowsocks-libev-2.4.5/.configured_yyn' failed
make[3]: *** [/home/lo/OpenWrt-SDK-15.05.1/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/shadowsocks-libev/openssl/shadowsocks-libev-2.4.5/.configured_yyn] Error 77
make[3]: Leaving directory '/home/lo/OpenWrt-SDK-15.05.1/package/shadowsocks-libev'
package/Makefile:191: recipe for target 'package/shadowsocks-libev/compile' failed
make[2]: *** [package/shadowsocks-libev/compile] Error 2
make[2]: Leaving directory '/home/lo/OpenWrt-SDK-15.05.1'
package/Makefile:188: recipe for target '/home/lo/OpenWrt-SDK-15.05.1/staging_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/stamp/.package_compile' failed
make[1]: *** [/home/lo/OpenWrt-SDK-15.05.1/staging_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/stamp/.package_compile] Error 2
make[1]: Leaving directory '/home/lo/OpenWrt-SDK-15.05.1'
/home/lo/OpenWrt-SDK-15.05.1/include/toplevel.mk:174: recipe for target 'world' failed
make: *** [world] Error 2

luci界面编译正常！！

如何自建一台可信DNS？

最近加入的可信dns这个feature还是挺有意思的，但怎么能拥有一台可信DNS呢？如果DNS放在国外，肯定会被污染，如果通过ss-tunnel连接，那不是又回到老路了吗？如果DNS放在国内，那如何能做到可信？不知道有什么手段能建立一台可信DNS。

停用chinadns之后，网址无法解析

停用chinadns
LuCI 中定位至「网络 - DHCP/DNS」
「基本设置」本地服务器留空
「HOSTS和解析文件」取消勾选忽略解析文件
重启路由，网址无法解析

ChinaDNS在路由器的/etc/config/没有chinadns文件，导致luci-app-chinadns无法启用

你好！
很感谢您开发并维护的chinadns for openwrt版。在luci-app-chinadns发布后，在编译openwrt固件的时候始终在luci界面找不到。shadowsocks的可以。今天偶尔看了一下openwrt-dist-luci目录里的文件，发现chinadns.lua文件中有判断语句：
function index()
if not nixio.fs.access("/etc/config/chinadns") then
return
end
而在openwrt的SDK中选择chiandns和luci-app-chinadns后编译完成的固件中，/etc/config目录里并没有chinadns文件，shadowssocks文件是有的。刚才手动创建了一个，现在在luci的配置界面可以看到chinadns了。
可否改进一下？谢谢！

ar71xx平台下安装有遇到错误信息

Collected errors:

pkg_run_script: package "shadowsocks-libev-spec" postinst script returned status 127.
opkg_configure: shadowsocks-libev-spec.postinst returned 127.
pkg_run_script: package "ChinaDNS" postinst script returned status 127.
opkg_configure: ChinaDNS.postinst returned 127.
pkg_run_script: package "ShadowVPN" postinst script returned status 127.
opkg_configure: ShadowVPN.postinst returned 127.

不知道具体是什么。贴出来反馈下。

请问我安装了chinadns和luci-app-chinadns后，luci里没有chinadns的选项是为什么？

路由是网件4300 v1
固件版本：OpenWrt Chaos Calmer 15.05 / LuCI (git-15.248.30277-3836b45)
内核版本：3.18.20
ChinaDNS版本是ChinaDNS_1.3.2-3_ar71xx
luci-app-ChinaDNS版本是luci-app-chinadns_1.3.4-1_all

修改启动脚本自动配置dnsmasq。

start() {
config_load chinadns
config_foreach start_chinadns chinadns
poort=echo "$parms $1" | awk '{print $2}'
uci del dhcp.@dnsmasq[-1].server
if [ -n "$poort" ];then
uci set dhcp.@dnsmasq[-1].noresolv=1
uci add_list dhcp.@dnsmasq[-1].server=127.0.0.1#$poort
uci commit dhcp
/etc/init.d/dnsmasq restart
else
echo " exit!!!"
fi

}

stop() {
service_stop /usr/bin/chinadns
uci del dhcp.@dnsmasq[-1].server
uci set dhcp.@dnsmasq[-1].noresolv=0
uci commit dhcp
/etc/init.d/dnsmasq restart
}

chindns配合pdnsd的问题

发现pdnsd配合chinadns用udp方式查询dns的速度很快，请问用udp方式查询好国外非53端口的dns服务器会被污染dns吗？(服务器是用pdnsd搭建的)

可信DNS比国内DNS先返回结果

如果可信DNS比国内DNS先返回结果，则会采用可信DNS的返回结果而不是国内DNS的返回结果，会造成国内网站被解析到了海外CDN的地址，此问题如何解决？

关于53端口的转发

您好！
我看到官方的init脚本里面有这个重定向规则，而openwrt面却没有！

iptables -t nat -A PREROUTING -p udp --dport 53 -j REDIRECT --to-ports 5353

请问这个跟server=127.0.0.1#5353一样？所以就没必要再转发？

ss-tunnel

需要服务端怎么设置

怎么够使用国内纯净DNS

在上游服务器选项中，第二个服务器想使用自建的在国内的纯净DNS，但是提示必须使用国外的IP，应该怎么设置？

请问有搭建shadowvpn的教程么

网上找的源都是 clowwindy被删掉的。。

请问这个openwrt-chinadns和clowwindy的原始版本有什么区别呢？

如题，请问这个openwrt-chinadns和clowwindy的原始版本ChinaDNS-C有什么区别呢？有新的改进吗？

--braveguywallce

同时运行 chinadns 和openwrt脚本的时候因为都是下载的master.zip 互相覆盖所以会报错

PKG_SOURCE_URL:=https://github.com/clowwindy/ChinaDNS-C/releases/download/$(PKG_VERSION)
PKG_SOURCE:=chinadns-c-$(PKG_VERSION).tar.gz
PKG_MAINTAINER:=clowwindy [email protected]

can you build a bin for "mvebu"

i had a router "linksys wrt1900ac" , so i need this bin. thank you.

Still being poisoned

I've set up OpenWrt+shadowsocks-libev+ChinaDNS on my router and it works great. Trying on a friends now, has a 4mb flash so I used the polarssl builds.

I've managed to get shadowsocks-libev-polarssl working and have installed ChinaDNS but can only visit google/gmail, no other blocked sites. I'm new to OpenWrt so I've probably missed something but I've been trying for hours, any ideas?

国内小运营商网络访问cdn节点

本人最近使用北京网邻宽带——一家覆盖面积只有几平方公里的宽带运营商的网络——使用chinadns时不时ps4走国外的cdn节点。
然后不经意间，我发现了：
PING www.a.shifen.com (220.181.111.188): 56 data bytes
64 bytes from 220.181.111.188: icmp_seq=0 ttl=52 time=10.245 ms
64 bytes from 220.181.111.188: icmp_seq=1 ttl=52 time=16.607 ms
64 bytes from 220.181.111.188: icmp_seq=2 ttl=52 time=24.203 ms
64 bytes from 220.181.111.188: icmp_seq=3 ttl=52 time=6.583 ms
64 bytes from 220.181.111.188: icmp_seq=4 ttl=52 time=7.546 ms
64 bytes from 220.181.111.188: icmp_seq=5 ttl=52 time=11.021 ms
64 bytes from 220.181.111.188: icmp_seq=6 ttl=52 time=21.882 ms
64 bytes from 220.181.111.188: icmp_seq=7 ttl=52 time=8.396 ms
64 bytes from 220.181.111.188: icmp_seq=8 ttl=52 time=7.035 ms
64 bytes from 220.181.111.188: icmp_seq=9 ttl=52 time=7.112 ms
64 bytes from 220.181.111.188: icmp_seq=10 ttl=52 time=12.095 ms
64 bytes from 220.181.111.188: icmp_seq=11 ttl=52 time=8.043 ms
64 bytes from 220.181.111.188: icmp_seq=12 ttl=52 time=147.277 ms
64 bytes from 220.181.111.188: icmp_seq=13 ttl=52 time=7.625 ms
64 bytes from 220.181.111.188: icmp_seq=14 ttl=52 time=6.483 ms
64 bytes from 220.181.111.188: icmp_seq=15 ttl=52 time=8.829 ms
64 bytes from 220.181.111.188: icmp_seq=16 ttl=52 time=6.981 ms
64 bytes from 220.181.111.188: icmp_seq=17 ttl=52 time=8.043 ms
64 bytes from 220.181.111.188: icmp_seq=18 ttl=52 time=7.470 ms
64 bytes from 220.181.111.188: icmp_seq=19 ttl=52 time=6.447 ms
64 bytes from 220.181.111.188: icmp_seq=20 ttl=52 time=9.046 ms
64 bytes from 220.181.111.188: icmp_seq=21 ttl=52 time=6.596 ms
64 bytes from 220.181.111.188: icmp_seq=22 ttl=52 time=8.473 ms
64 bytes from 220.181.111.188: icmp_seq=23 ttl=52 time=7.468 ms
64 bytes from 220.181.111.188: icmp_seq=24 ttl=52 time=109.848 ms

没错，这小运营商的网络极不稳定，连baidu.com的延迟变化幅度极大。也就是说查询cdn节点时，国内dns返回时间可能比国外要长，然后chinadns直接使用了先返回的国外节点。
目前，我用下面的dns：
219.141.140.10,219.141.136.10,202.106.196.115,202.106.0.20,127.0.0.1:5300
四个北京dns（网通+电信） vs 一个国外dns（谷歌）
然而依旧有可能走国外节点（有几成概率吧）：
PING sonycoment.vo.llnwd.net (203.77.188.253): 56 data bytes
64 bytes from 203.77.188.253: icmp_seq=0 ttl=43 time=189.938 ms
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 203.77.188.253: icmp_seq=4 ttl=43 time=188.064 ms
^C
--- sonycoment.vo.llnwd.net ping statistics ---
5 packets transmitted, 2 packets received, 60.0% packet loss

真是日了狗了。

nslookup gs2.ww.prod.dl.playstation.net
;; Truncated, retrying in TCP mode.
Server: 192.168.1.1
Address: 192.168.1.1#53

** server can't find gs2.ww.prod.dl.playstation.net: NXDOMAIN

建议

目前采用chinadns + shadowsocks 开启UDP进行dns解析的模式来处理dns污染。

目前存在的问题：
有时候一个国外的域名，同时采用114.114.114.114 和本机的127.0.0.1:1080 （这里最终走ss）进行dns查询。有时候ss的没有返回，而114.114.114.114 返回了真实的IP地址。这时候浏览器就不能打开网页了，因为国内的dns应答被过滤掉了，而国外的dns没有应答，这样就出错了。

我的想法是：对于国外的域名或IP地址，如果国内的有应答了，就把它存起来，等带国外的结果，如果超过0.3秒还没有应答，就已国内的dns应答为结果返回。这样就可以解救有些时候不能上网的问题，然后过一段时间又可以了。

你好，我是小米路由器没有openwrt官方的sdk，只有小米发布的交叉编译工具链，请问如何编译？

1.3.2-1版本无法返回结果

我的ChinaDNS版本为1.3.2-1，症状为在国内加速列表accelerated-domains.china.conf和国外 foreign_list.conf 这两个列表外的域名会出现ERR_NAME_NOT_RESOLVED。

digChinaDNS信息如下，没有返回结果，

C:\Users\szx42>dig @192.168.1.1 -p 35353 interfacelift.com

; <<>> DiG 9.10.2-P4 <<>> @192.168.1.1 -p 35353 interfacelift.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 55980
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; WARNING: EDNS query returned status FORMERR - retry with '+noedns'

;; QUESTION SECTION:
;interfacelift.com. IN A

;; Query time: 195 msec
;; SERVER: 192.168.1.1#35353(192.168.1.1)
;; WHEN: Thu Sep 03 17:03:13 ?D1ú±ê×?ê±?? 2015
;; MSG SIZE rcvd: 36

dig远端非标dns服务器如下，返回正常，

C:\Users\szx42>dig @... -p 5050 interfacelift.com

; <<>> DiG 9.10.2-P4 <<>> @... -p 5050 interfacelift.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39281
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
interfacelift.com. 900 IN A 206.190.152.82

;; Query time: 275 msec
;; SERVER: 192.243.118.182#5050(192.243.118.182)
;; WHEN: Thu Sep 03 17:03:29 ?D1ú±ê×?ê±?? 2015
;; MSG SIZE rcvd: 62

再次dig ChinaDNS，有结果了。。。。。
C:\Users\szx42>dig @192.168.1.1 -p 35353 interfacelift.com

; <<>> DiG 9.10.2-P4 <<>> @192.168.1.1 -p 35353 interfacelift.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7233
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;interfacelift.com. IN A

;; ANSWER SECTION:
interfacelift.com. 897 IN A 206.190.152.82

;; Query time: 184 msec
;; SERVER: 192.168.1.1#35353(192.168.1.1)
;; WHEN: Thu Sep 03 17:03:32 ?D1ú±ê×?ê±?? 2015

;; MSG SIZE rcvd: 52

后续再向chinadns查询还是不正常，没有返回结果，具体多久就失效了我还没测试。。
其他不在那两个列表里面的域名都是这种情况，互不干扰。。。
root@OpenWrt:~# chinadns -v
Thu Sep 3 17:48:01 2015 CHNROUTE_FILE not specified, CHNRoute is disabled
Thu Sep 3 17:48:01 2015 chinadns.c:554 bind: Address already in use
Thu Sep 3 17:48:01 2015 Can't bind address 0.0.0.0:53
可以确定国内路由表没有问题，如图。

root@OpenWrt:~# chinadns -c /etc/chinadns_chnroute.txt
Thu Sep 3 18:03:50 2015 chinadns.c:554 bind: Address already in use
Thu Sep 3 18:03:50 2015 Can't bind address 0.0.0.0:53

root@OpenWrt:~# chinadns -h
usage: chinadns [-h] [-l IPLIST_FILE] [-b BIND_ADDR] [-p BIND_PORT]
[-c CHNROUTE_FILE] [-s DNS] [-m] [-v] [-V]
Forward DNS requests.

-l IPLIST_FILE path to ip blacklist file
-c CHNROUTE_FILE path to china route file
if not specified, CHNRoute will be turned
-d off enable bi-directional CHNRoute filter
-y delay time for suspects, default: 0.3
-b BIND_ADDR address that listens, default: 127.0.0.1
-p BIND_PORT port that listens, default: 53
-s DNS DNS servers to use, default:
114.114.114.114,208.67.222.222:443,8.8.8.8
-m use DNS compression pointer mutation
(backlist and delaying would be disabled)
-v verbose logging
-h show this help message and exit
-V print version and exit

Online help: https://github.com/clowwindy/ChinaDNS

root@OpenWrt:~# chinadns -m -c /etc/chinadns_chnroute.txt
Thu Sep 3 18:06:58 2015 chinadns.c:554 bind: Address already in use
Thu Sep 3 18:06:58 2015 Can't bind address 0.0.0.0:53

求助。。。。

Could I use Shadowvpn as the upstream dns server?

Would the dns query result be polluted when I set 10.7.0.1:53 as the upstream sever of ChinaDNS?

Now my Shadowvpn works well. Its gateway is 10.7.0.1.
And I have installed pdnsd on my host listening port 53.
I wonder if that all the traffic walks through tun0(10.7.0.1) is encrypted?
My idea is that let dns request walk through Shadowvpn to prevent GFW dns pollution.

请问Chinadns和dnsmasq功能重复了吗？

用了其中一种，就不需要另外一种了是吧

从1.3.2后某些网站解析失败

snt146.mail.live.com这个是微软邮箱的域名，使用最新的1.3.2会偶尔出现无法解析。
我发现从1.3.2后的luci-app没有了“取消压缩指针”这一项。
现在把版本降级为1.3.1。关掉压缩指针就能正确解析了。

某些网站在使用Chinadns 1.3.2也会出现无法解析。

双向过滤可能存在bug

国内返回的部分结果也被过滤了。
版本为1.3.2-3
启动参数：
/usr/bin/chinadns -p 5353 -s 218.2.135.1,127.0.0.1:5300 -c /etc/chinadns_chnroute.txt -d -m

日志

Sat Apr 16 10:17:18 2016 request news.sina.com.cn from 218.2.135.1:53 127.0.0.1:5300
Sat Apr 16 10:17:18 2016 response news.sina.com.cn from 218.2.135.1:53 - pass
Sat Apr 16 10:17:18 2016 response news.sina.com.cn from 127.0.0.1:5300 - pass

在/etc/chinadns_chnroute.txt的末尾，我强行指定dns服务器和新浪南京服务器为国内（原本这两个ip也在路由表中）：

在PC上使用路由器dns服务器查询超时：

其他设置：

openwrt15.05问题

首先表示感谢，用了很久了
昨天全新刷机到openwrt15.05正式版，安装ChinaDNS_1.3.2_ar71xx.ipk和luci-app-chinadns_1.3.4-1_all.ipk
openwrt的配置界面怎么都找不到chindns，最后翻了很多帖子，才发现要在/etc/config/下面建立chinadns文件，内容来自源码包里的chinadns.config，我记得之前14.07安装1.3.0时好像没有这个问题，请检查一下，谢谢！

无法解析某些域名

chinadns版本是最新版，上游服务器为114.114.114.114,8.8.4.4

举例
root@OpenWrt:~# dig ss06.8ke.co

; <<>> DiG 9.9.4 <<>> ss06.8ke.co
;; global options: +cmd
;; connection timed out; no servers could be reached
root@OpenWrt:~# dig ss06.8ke.co @8.8.8.8

; <<>> DiG 9.9.4 <<>> ss06.8ke.co @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52542
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ss06.8ke.co. IN A

;; ANSWER SECTION:
ss06.8ke.co. 35 IN A 103.226.125.101
ss06.8ke.co. 35 IN A 207.226.143.34
ss06.8ke.co. 35 IN A 118.193.150.214

;; Query time: 120 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Feb 11 22:35:21 CST 2015
;; MSG SIZE rcvd: 88

请问新版本中的双向过滤的意思是？

新版本更新了什么样的防污染策略还不是很清楚，求解释一下双向过滤，感谢！

chinadns使用一段时间后出现不能解析国外IP情况！

chinadns使用一段时间后出现不能解析国外IP情况，国内解析正常！
重启很多次chinadns才能恢复！

Mon Oct 26 13:24:54 2015 request www.google.com
Mon Oct 26 13:24:54 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.36, filter
Mon Oct 26 13:24:54 2015 response www.google.com from 208.67.222.222:443 - 216.58.221.68, delay
Mon Oct 26 13:25:06 2015 request www.google.co.jp
Mon Oct 26 13:25:06 2015 request www.google.com
Mon Oct 26 13:25:06 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:06 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:06 2015 request www.google.com
Mon Oct 26 13:25:06 2015 request www.google.co.jp
Mon Oct 26 13:25:06 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:06 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:07 2015 request www.google.com
Mon Oct 26 13:25:07 2015 request www.google.co.jp
Mon Oct 26 13:25:07 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:07 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:09 2015 request www.google.com
Mon Oct 26 13:25:09 2015 request www.google.co.jp
Mon Oct 26 13:25:09 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:09 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:13 2015 request www.google.co.jp
Mon Oct 26 13:25:13 2015 request www.google.com
Mon Oct 26 13:25:13 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:13 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:17 2015 request www.google.com
Mon Oct 26 13:25:17 2015 request google.com
Mon Oct 26 13:25:17 2015 request google.com
Mon Oct 26 13:25:17 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:17 2015 response google.com from 211.139.29.170:53 - 74.125.204.102, filter
Mon Oct 26 13:25:17 2015 response google.com from 211.139.29.170:53 - 74.125.204.102, filter
Mon Oct 26 13:25:17 2015 request www.googleapis.com
Mon Oct 26 13:25:17 2015 response www.googleapis.com from 211.139.29.170:53 - 64.233.188.95, filter
Mon Oct 26 13:25:17 2015 request www.google.com
Mon Oct 26 13:25:17 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:17 2015 request www.googleapis.com
Mon Oct 26 13:25:17 2015 response www.googleapis.com from 211.139.29.170:53 - 64.233.188.95, filter
Mon Oct 26 13:25:18 2015 request google.com
Mon Oct 26 13:25:18 2015 response google.com from 211.139.29.170:53 - 74.125.204.102, filter
Mon Oct 26 13:25:18 2015 request www.google.com
Mon Oct 26 13:25:18 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:18 2015 request www.googleapis.com
Mon Oct 26 13:25:18 2015 response www.googleapis.com from 211.139.29.170:53 - 74.125.204.95, filter
Mon Oct 26 13:25:19 2015 request clients4.google.com
Mon Oct 26 13:25:19 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:19 2015 request down.verify.stat.xunlei.com
Mon Oct 26 13:25:19 2015 response down.verify.stat.xunlei.com from 211.139.29.170:53 - 183.224.3.54, delay
Mon Oct 26 13:25:19 2015 request clients4.google.com
Mon Oct 26 13:25:19 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:20 2015 request clients4.google.com
Mon Oct 26 13:25:20 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:20 2015 request www.google.com
Mon Oct 26 13:25:20 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:20 2015 request www.googleapis.com
Mon Oct 26 13:25:20 2015 response www.googleapis.com from 211.139.29.170:53 - 74.125.204.95, filter
Mon Oct 26 13:25:22 2015 request clients4.google.com
Mon Oct 26 13:25:22 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:24 2015 request www.google.com
Mon Oct 26 13:25:24 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:24 2015 request www.googleapis.com
Mon Oct 26 13:25:24 2015 response www.googleapis.com from 211.139.29.170:53 - 74.125.204.95, filter
Mon Oct 26 13:25:26 2015 request clients4.google.com
Mon Oct 26 13:25:26 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:28 2015 request www.google.com
Mon Oct 26 13:25:28 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:29 2015 request www.google.com
Mon Oct 26 13:25:29 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:30 2015 request register.mesh.com
Mon Oct 26 13:25:30 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.197, filter
Mon Oct 26 13:25:30 2015 request www.google.com
Mon Oct 26 13:25:30 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:30 2015 request register.mesh.com
Mon Oct 26 13:25:30 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.197, filter
Mon Oct 26 13:25:31 2015 request register.mesh.com
Mon Oct 26 13:25:31 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:25:32 2015 request www.google.com
Mon Oct 26 13:25:32 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:33 2015 request register.mesh.com
Mon Oct 26 13:25:33 2015 request www.google.co.jp
Mon Oct 26 13:25:33 2015 request clients5.google.com
Mon Oct 26 13:25:33 2015 request apis.google.com
Mon Oct 26 13:25:33 2015 request lh3.googleusercontent.com
Mon Oct 26 13:25:33 2015 request play.google.com
Mon Oct 26 13:25:33 2015 request plus.google.com
Mon Oct 26 13:25:33 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:25:33 2015 response apis.google.com from 211.139.29.170:53 - 74.125.203.139, filter
Mon Oct 26 13:25:33 2015 response play.google.com from 211.139.29.170:53 - 216.58.221.238, filter
Mon Oct 26 13:25:33 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:33 2015 response plus.google.com from 211.139.29.170:53 - 159.106.121.75, filter
Mon Oct 26 13:25:33 2015 response lh3.googleusercontent.com from 211.139.29.170:53 - 173.194.72.132, filter
Mon Oct 26 13:25:33 2015 response clients5.google.com from 211.139.29.170:53 - 74.125.23.101, filter
Mon Oct 26 13:25:33 2015 request www.google.co.jp
Mon Oct 26 13:25:33 2015 request play.google.com
Mon Oct 26 13:25:33 2015 request clients5.google.com
Mon Oct 26 13:25:33 2015 request apis.google.com
Mon Oct 26 13:25:33 2015 request lh3.googleusercontent.com
Mon Oct 26 13:25:33 2015 request plus.google.com
Mon Oct 26 13:25:33 2015 response play.google.com from 211.139.29.170:53 - 216.58.221.238, filter
Mon Oct 26 13:25:33 2015 response clients5.google.com from 211.139.29.170:53 - 74.125.23.101, filter
Mon Oct 26 13:25:33 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:33 2015 response apis.google.com from 211.139.29.170:53 - 74.125.203.139, filter
Mon Oct 26 13:25:33 2015 response plus.google.com from 211.139.29.170:53 - 159.106.121.75, filter
Mon Oct 26 13:25:33 2015 response lh3.googleusercontent.com from 211.139.29.170:53 - 173.194.72.132, filter
Mon Oct 26 13:25:34 2015 request www.google.co.jp
Mon Oct 26 13:25:34 2015 request clients5.google.com
Mon Oct 26 13:25:34 2015 request apis.google.com
Mon Oct 26 13:25:34 2015 request play.google.com
Mon Oct 26 13:25:34 2015 request lh3.googleusercontent.com
Mon Oct 26 13:25:34 2015 request plus.google.com
Mon Oct 26 13:25:34 2015 response clients5.google.com from 211.139.29.170:53 - 74.125.23.101, filter
Mon Oct 26 13:25:34 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:34 2015 response apis.google.com from 211.139.29.170:53 - 74.125.203.139, filter
Mon Oct 26 13:25:34 2015 response plus.google.com from 211.139.29.170:53 - 159.106.121.75, filter
Mon Oct 26 13:25:34 2015 response lh3.googleusercontent.com from 211.139.29.170:53 - 173.194.72.132, filter
Mon Oct 26 13:25:34 2015 response play.google.com from 211.139.29.170:53 - 216.58.221.238, filter
Mon Oct 26 13:25:36 2015 request www.google.com
Mon Oct 26 13:25:36 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:25:36 2015 request www.google.co.jp
Mon Oct 26 13:25:36 2015 request clients5.google.com
Mon Oct 26 13:25:36 2015 request lh3.googleusercontent.com
Mon Oct 26 13:25:36 2015 request play.google.com
Mon Oct 26 13:25:36 2015 request apis.google.com
Mon Oct 26 13:25:36 2015 request plus.google.com
Mon Oct 26 13:25:36 2015 response lh3.googleusercontent.com from 211.139.29.170:53 - 173.194.72.132, filter
Mon Oct 26 13:25:36 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:36 2015 response clients5.google.com from 211.139.29.170:53 - 74.125.23.101, filter
Mon Oct 26 13:25:36 2015 response apis.google.com from 211.139.29.170:53 - 74.125.203.139, filter
Mon Oct 26 13:25:36 2015 response plus.google.com from 211.139.29.170:53 - 159.106.121.75, filter
Mon Oct 26 13:25:36 2015 response play.google.com from 211.139.29.170:53 - 216.58.221.238, filter
Mon Oct 26 13:25:37 2015 request register.mesh.com
Mon Oct 26 13:25:37 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:25:40 2015 request down.verify.stat.xunlei.com
Mon Oct 26 13:25:40 2015 response down.verify.stat.xunlei.com from 211.139.29.170:53 - 183.224.3.55, delay
Mon Oct 26 13:25:40 2015 request www.google.co.jp
Mon Oct 26 13:25:40 2015 request play.google.com
Mon Oct 26 13:25:40 2015 request clients5.google.com
Mon Oct 26 13:25:40 2015 request apis.google.com
Mon Oct 26 13:25:40 2015 request lh3.googleusercontent.com
Mon Oct 26 13:25:40 2015 request plus.google.com
Mon Oct 26 13:25:40 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:25:40 2015 response apis.google.com from 211.139.29.170:53 - 74.125.203.139, filter
Mon Oct 26 13:25:40 2015 response lh3.googleusercontent.com from 211.139.29.170:53 - 173.194.72.132, filter
Mon Oct 26 13:25:40 2015 response play.google.com from 211.139.29.170:53 - 216.58.221.238, filter
Mon Oct 26 13:25:40 2015 response plus.google.com from 211.139.29.170:53 - 159.106.121.75, filter
Mon Oct 26 13:25:40 2015 response clients5.google.com from 211.139.29.170:53 - 74.125.23.101, filter
Mon Oct 26 13:25:44 2015 request hao.qq.com
Mon Oct 26 13:25:44 2015 response hao.qq.com from 211.139.29.170:53 - 111.30.131.119, pass
Mon Oct 26 13:25:44 2015 request clients4.google.com
Mon Oct 26 13:25:44 2015 request ssl.gstatic.com
Mon Oct 26 13:25:44 2015 request c.gj.qq.com
Mon Oct 26 13:25:44 2015 request www.baidu.com
Mon Oct 26 13:25:44 2015 response ssl.gstatic.com from 211.139.29.170:53 - 216.58.221.67, filter
Mon Oct 26 13:25:44 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:44 2015 response www.baidu.com from 211.139.29.170:53 - 111.13.100.92, 111.13.100.91, pass
Mon Oct 26 13:25:44 2015 response c.gj.qq.com from 211.139.29.170:53 - 211.136.233.115, 211.136.233.101, 211.136.233.105, 211.136.233.106, 211.136.233.114, pass
Mon Oct 26 13:25:44 2015 request user.stat.xmp.xunlei.com
Mon Oct 26 13:25:44 2015 response user.stat.xmp.xunlei.com from 211.139.29.170:53 - 122.143.5.5, 163.177.79.183, pass
Mon Oct 26 13:25:44 2015 request conf.xmp.xunlei.com
Mon Oct 26 13:25:44 2015 request conf.xmp.kankan.com
Mon Oct 26 13:25:44 2015 response conf.xmp.xunlei.com from 211.139.29.170:53 - 120.210.196.212, pass
Mon Oct 26 13:25:44 2015 response conf.xmp.kankan.com from 211.139.29.170:53 - 183.224.3.53, delay
Mon Oct 26 13:25:45 2015 request masterconn.qq.com
Mon Oct 26 13:25:45 2015 response masterconn.qq.com from 211.139.29.170:53 - 117.144.246.144, 117.144.246.145, 120.204.200.124, 117.135.129.68, 117.144.246.143, 140.207.125.125, 140.207.125.126, pass
Mon Oct 26 13:25:45 2015 request masterconn2.qq.com
Mon Oct 26 13:25:45 2015 response masterconn2.qq.com from 211.139.29.170:53 - 183.224.1.135, delay
Mon Oct 26 13:25:45 2015 request ssl.gstatic.com
Mon Oct 26 13:25:45 2015 request clients4.google.com
Mon Oct 26 13:25:45 2015 response ssl.gstatic.com from 211.139.29.170:53 - 216.58.221.67, filter
Mon Oct 26 13:25:45 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:45 2015 request p2.qq.sogoucdn.com
Mon Oct 26 13:25:45 2015 request p3.qq.sogoucdn.com
Mon Oct 26 13:25:45 2015 response p2.qq.sogoucdn.com from 211.139.29.170:53 - 117.172.7.132, 117.172.7.133, pass
Mon Oct 26 13:25:45 2015 response p3.qq.sogoucdn.com from 211.139.29.170:53 - 117.172.7.133, 117.172.7.132, pass
Mon Oct 26 13:25:45 2015 request p0.123.sogoucdn.com
Mon Oct 26 13:25:45 2015 response p0.123.sogoucdn.com from 211.139.29.170:53 - 120.192.86.74, 183.203.13.195, 183.203.13.196, 183.203.13.197, 183.203.13.200, 120.192.86.68, 120.192.86.70, pass
Mon Oct 26 13:25:45 2015 request bho.xl7.xunlei.com
Mon Oct 26 13:25:45 2015 request www.sogou.com
Mon Oct 26 13:25:45 2015 response bho.xl7.xunlei.com from 211.139.29.170:53 - 42.51.169.157, 42.51.169.158, 42.51.169.163, pass
Mon Oct 26 13:25:45 2015 response www.sogou.com from 211.139.29.170:53 - 111.13.96.215, 111.13.96.216, 111.13.96.217, 111.13.96.214, pass
Mon Oct 26 13:25:46 2015 request p1.qq.sogoucdn.com
Mon Oct 26 13:25:46 2015 request nat.emule.org.cn
Mon Oct 26 13:25:46 2015 response p1.qq.sogoucdn.com from 211.139.29.170:53 - 117.172.7.133, 117.172.7.132, pass
Mon Oct 26 13:25:46 2015 response nat.emule.org.cn from 211.139.29.170:53 - delay
Mon Oct 26 13:25:46 2015 request p2.123.sogoucdn.com
Mon Oct 26 13:25:46 2015 response p2.123.sogoucdn.com from 211.139.29.170:53 - 183.224.3.54, delay
Mon Oct 26 13:25:46 2015 request p3.123.sogoucdn.com
Mon Oct 26 13:25:46 2015 response p3.123.sogoucdn.com from 211.139.29.170:53 - 183.224.1.153, delay
Mon Oct 26 13:25:46 2015 request upd1.sogoucdn.com
Mon Oct 26 13:25:46 2015 request ssl.gstatic.com
Mon Oct 26 13:25:46 2015 request clients4.google.com
Mon Oct 26 13:25:46 2015 response upd1.sogoucdn.com from 211.139.29.170:53 - 117.187.19.164, pass
Mon Oct 26 13:25:46 2015 response ssl.gstatic.com from 211.139.29.170:53 - 216.58.221.67, filter
Mon Oct 26 13:25:46 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:46 2015 request d.123.sogoucdn.com
Mon Oct 26 13:25:46 2015 response d.123.sogoucdn.com from 211.139.29.170:53 - 117.185.13.179, 117.185.13.178, pass
Mon Oct 26 13:25:46 2015 request p4.123.sogoucdn.com
Mon Oct 26 13:25:46 2015 response p4.123.sogoucdn.com from 211.139.29.170:53 - 183.224.3.53, delay
Mon Oct 26 13:25:46 2015 request nat.emule.org.cn
Mon Oct 26 13:25:46 2015 response nat.emule.org.cn from 211.139.29.170:53 - delay
Mon Oct 26 13:25:46 2015 request pb.sogou.com
Mon Oct 26 13:25:46 2015 response pb.sogou.com from 211.139.29.170:53 - 111.13.96.214, 111.13.96.215, 111.13.96.216, 111.13.96.217, pass
Mon Oct 26 13:25:46 2015 request nat.emule.org.cn
Mon Oct 26 13:25:46 2015 response nat.emule.org.cn from 211.139.29.170:53 - delay
Mon Oct 26 13:25:46 2015 request p1.123.sogoucdn.com
Mon Oct 26 13:25:46 2015 response p1.123.sogoucdn.com from 211.139.29.170:53 - 183.224.3.56, delay
Mon Oct 26 13:25:47 2015 request nat.emule.org.cn
Mon Oct 26 13:25:47 2015 response nat.emule.org.cn from 211.139.29.170:53 - delay
Mon Oct 26 13:25:47 2015 request nat.emule.org.cn
Mon Oct 26 13:25:47 2015 response nat.emule.org.cn from 211.139.29.170:53 - delay
Mon Oct 26 13:25:47 2015 request nat.emule.org.cn
Mon Oct 26 13:25:47 2015 response nat.emule.org.cn from 211.139.29.170:53 - delay
Mon Oct 26 13:25:48 2015 request ssl.gstatic.com
Mon Oct 26 13:25:48 2015 request clients4.google.com
Mon Oct 26 13:25:48 2015 response ssl.gstatic.com from 211.139.29.170:53 - 216.58.221.67, filter
Mon Oct 26 13:25:48 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:50 2015 request masterconn2.qq.com
Mon Oct 26 13:25:50 2015 response masterconn2.qq.com from 211.139.29.170:53 - 183.224.1.133, delay
Mon Oct 26 13:25:51 2015 request www.baidu.com
Mon Oct 26 13:25:51 2015 response www.baidu.com from 211.139.29.170:53 - 111.13.100.92, 111.13.100.91, pass
Mon Oct 26 13:25:51 2015 request ss1.bdstatic.com
Mon Oct 26 13:25:51 2015 request urs.microsoft.com
Mon Oct 26 13:25:51 2015 response ss1.bdstatic.com from 211.139.29.170:53 - 183.232.22.32, pass
Mon Oct 26 13:25:51 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:25:52 2015 request urs.microsoft.com
Mon Oct 26 13:25:52 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:25:52 2015 request clients4.google.com
Mon Oct 26 13:25:52 2015 request ssl.gstatic.com
Mon Oct 26 13:25:52 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:25:52 2015 response ssl.gstatic.com from 211.139.29.170:53 - 216.58.221.67, filter
Mon Oct 26 13:25:53 2015 request sp0.baidu.com
Mon Oct 26 13:25:53 2015 response sp0.baidu.com from 211.139.29.170:53 - 111.13.100.92, 111.13.100.91, pass
Mon Oct 26 13:25:53 2015 request urs.microsoft.com
Mon Oct 26 13:25:53 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:25:55 2015 request urs.microsoft.com
Mon Oct 26 13:25:55 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:25:55 2015 request formi.baidu.com
Mon Oct 26 13:25:55 2015 response formi.baidu.com from 211.139.29.170:53 - 183.224.3.55, delay
Mon Oct 26 13:25:59 2015 request urs.microsoft.com
Mon Oct 26 13:25:59 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:25:59 2015 request clients4.google.com
Mon Oct 26 13:25:59 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:00 2015 request clients4.google.com
Mon Oct 26 13:26:00 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:00 2015 request ss0.baidu.com
Mon Oct 26 13:26:00 2015 response ss0.baidu.com from 211.139.29.170:53 - 183.232.22.33, pass
Mon Oct 26 13:26:01 2015 request clients4.google.com
Mon Oct 26 13:26:01 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:03 2015 request urs.microsoft.com
Mon Oct 26 13:26:03 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:26:03 2015 request clients4.google.com
Mon Oct 26 13:26:03 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:03 2015 request urs.microsoft.com
Mon Oct 26 13:26:03 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:26:04 2015 request sp3.baidu.com
Mon Oct 26 13:26:04 2015 response sp3.baidu.com from 211.139.29.170:53 - 111.13.100.91, 111.13.100.92, pass
Mon Oct 26 13:26:04 2015 request urs.microsoft.com
Mon Oct 26 13:26:04 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:26:06 2015 request urs.microsoft.com
Mon Oct 26 13:26:06 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:26:07 2015 request clients4.google.com
Mon Oct 26 13:26:07 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:10 2015 request urs.microsoft.com
Mon Oct 26 13:26:10 2015 response urs.microsoft.com from 211.139.29.170:53 - 134.170.50.250, filter
Mon Oct 26 13:26:14 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:14 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:15 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:15 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:15 2015 request kkpgv3.xunlei.com
Mon Oct 26 13:26:15 2015 response kkpgv3.xunlei.com from 211.139.29.170:53 - 122.143.5.5, 163.177.79.183, pass
Mon Oct 26 13:26:15 2015 request clients4.google.com
Mon Oct 26 13:26:15 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:15 2015 request mapping.v.xunlei.com
Mon Oct 26 13:26:15 2015 response mapping.v.xunlei.com from 211.139.29.170:53 - 183.224.1.135, delay
Mon Oct 26 13:26:15 2015 request clients4.google.com
Mon Oct 26 13:26:15 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:16 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:16 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:16 2015 request clients4.google.com
Mon Oct 26 13:26:16 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:18 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:18 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:18 2015 request clients4.google.com
Mon Oct 26 13:26:18 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:22 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:22 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:22 2015 request clients4.google.com
Mon Oct 26 13:26:22 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:26 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:26 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:26 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:26 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:27 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:27 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:29 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:29 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:31 2015 request clients4.google.com
Mon Oct 26 13:26:31 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:31 2015 request clients4.google.com
Mon Oct 26 13:26:31 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:32 2015 request clients4.google.com
Mon Oct 26 13:26:32 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:33 2015 request iecvlist.microsoft.com
Mon Oct 26 13:26:33 2015 response iecvlist.microsoft.com from 211.139.29.170:53 - 192.229.145.200, filter
Mon Oct 26 13:26:34 2015 request clients4.google.com
Mon Oct 26 13:26:34 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:37 2015 request mapping.v.xunlei.com
Mon Oct 26 13:26:37 2015 response mapping.v.xunlei.com from 211.139.29.170:53 - 183.224.1.136, delay
Mon Oct 26 13:26:38 2015 request clients4.google.com
Mon Oct 26 13:26:38 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:41 2015 request register.mesh.com
Mon Oct 26 13:26:41 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:26:41 2015 request register.mesh.com
Mon Oct 26 13:26:41 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:26:42 2015 request register.mesh.com
Mon Oct 26 13:26:42 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:26:44 2015 request register.mesh.com
Mon Oct 26 13:26:44 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:26:47 2015 request clients4.google.com
Mon Oct 26 13:26:47 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:47 2015 request clients4.google.com
Mon Oct 26 13:26:47 2015 response clients4.google.com from 211.139.29.170:53 - 74.125.23.102, filter
Mon Oct 26 13:26:47 2015 response clients4.google.com from 208.67.222.222:443 - 74.125.23.101, 74.125.23.113, 74.125.23.102, 74.125.23.139, 74.125.23.138, 74.125.23.100, pass
Mon Oct 26 13:26:48 2015 request ssw.live.com
Mon Oct 26 13:26:48 2015 response ssw.live.com from 211.139.29.170:53 - 207.46.7.252, filter
Mon Oct 26 13:26:48 2015 response ssw.live.com from 208.67.222.222:443 - 207.46.7.252, pass
Mon Oct 26 13:26:48 2015 request register.mesh.com
Mon Oct 26 13:26:48 2015 response register.mesh.com from 211.139.29.170:53 - 65.55.194.198, filter
Mon Oct 26 13:26:48 2015 response register.mesh.com from 208.67.222.222:443 - 65.55.194.201, 65.55.194.202, 65.55.194.203, 65.55.194.204, 65.55.194.195, 65.55.194.196, 65.55.194.197, 65.55.194.198, 65.55.194.199, 65.55.194.200, pass
Mon Oct 26 13:27:04 2015 request www.google.co.jp
Mon Oct 26 13:27:04 2015 request www.google.com
Mon Oct 26 13:27:04 2015 response www.google.com from 211.139.29.170:53 - 216.58.221.132, filter
Mon Oct 26 13:27:04 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:27:04 2015 response www.google.com from 208.67.222.222:443 - 216.58.221.68, delay
Mon Oct 26 13:27:04 2015 response www.google.co.jp from 208.67.222.222:443 - 216.58.221.227, delay
Mon Oct 26 13:27:04 2015 request www.google.co.jp
Mon Oct 26 13:27:04 2015 response www.google.co.jp from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:27:04 2015 response www.google.co.jp from 208.67.222.222:443 - 216.58.221.227, delay
Mon Oct 26 13:27:05 2015 request clients5.google.com
Mon Oct 26 13:27:05 2015 request apis.google.com
Mon Oct 26 13:27:05 2015 request plus.google.com
Mon Oct 26 13:27:05 2015 request lh3.googleusercontent.com
Mon Oct 26 13:27:05 2015 request ssl.gstatic.com
Mon Oct 26 13:27:05 2015 response apis.google.com from 211.139.29.170:53 - 173.194.72.102, filter
Mon Oct 26 13:27:05 2015 response plus.google.com from 211.139.29.170:53 - 159.106.121.75, filter
Mon Oct 26 13:27:05 2015 response lh3.googleusercontent.com from 211.139.29.170:53 - 173.194.72.132, filter
Mon Oct 26 13:27:05 2015 response ssl.gstatic.com from 211.139.29.170:53 - 216.58.221.67, filter
Mon Oct 26 13:27:05 2015 response lh3.googleusercontent.com from 208.67.222.222:443 - 64.233.189.132, pass
Mon Oct 26 13:27:05 2015 response clients5.google.com from 211.139.29.170:53 - 74.125.23.101, filter
Mon Oct 26 13:27:05 2015 request play.google.com
Mon Oct 26 13:27:05 2015 response plus.google.com from 208.67.222.222:443 - 173.194.72.138, 173.194.72.113, 173.194.72.139, 173.194.72.100, 173.194.72.101, 173.194.72.102, pass
Mon Oct 26 13:27:05 2015 response clients5.google.com from 208.67.222.222:443 - 74.125.23.100, 74.125.23.102, 74.125.23.113, 74.125.23.139, 74.125.23.138, 74.125.23.101, pass
Mon Oct 26 13:27:05 2015 request www.gstatic.com
Mon Oct 26 13:27:05 2015 response play.google.com from 211.139.29.170:53 - 216.58.221.78, filter
Mon Oct 26 13:27:05 2015 response www.gstatic.com from 211.139.29.170:53 - 216.58.221.227, filter
Mon Oct 26 13:27:05 2015 response www.gstatic.com from 208.67.222.222:443 - 216.58.221.99, delay
Mon Oct 26 13:27:05 2015 response play.google.com from 208.67.222.222:443 - 216.58.221.78, pass
Mon Oct 26 13:27:05 2015 response apis.google.com from 208.67.222.222:443 - 74.125.203.113, 74.125.203.100, 74.125.203.139, 74.125.203.101, 74.125.203.138, 74.125.203.102, pass
Mon Oct 26 13:27:05 2015 response ssl.gstatic.com from 208.67.222.222:443 - 216.58.221.99, delay
Mon Oct 26 13:27:06 2015 request ssl.gstatic.com
Mon Oct 26 13:27:06 2015 response ssl.gstatic.com from 211.139.29.170:53 - 216.58.221.67, filter
Mon Oct 26 13:27:06 2015 response ssl.gstatic.com from 208.67.222.222:443 - 216.58.221.99, delay
Mon Oct 26 13:27:25 2015 request gfe.nvidia.com
Mon Oct 26 13:27:25 2015 response gfe.nvidia.com from 211.139.29.170:53 - 8.36.113.132, filter
Mon Oct 26 13:27:25 2015 response gfe.nvidia.com from 208.67.222.222:443 - 8.36.113.132, 8.36.120.226, pass
Mon Oct 26 13:27:25 2015 request imap.qq.com
Mon Oct 26 13:27:25 2015 response imap.qq.com from 211.139.29.170:53 - 183.232.121.188, 183.232.98.195, pass
Mon Oct 26 13:27:25 2015 response imap.qq.com from 208.67.222.222:443 - 183.232.98.195, 183.232.121.188, pass
Mon Oct 26 13:27:26 2015 request download.gfe.nvidia.com
Mon Oct 26 13:27:26 2015 response download.gfe.nvidia.com from 211.139.29.170:53 - 104.77.24.205, filter
Mon Oct 26 13:27:26 2015 response download.gfe.nvidia.com from 208.67.222.222:443 - 8.36.113.133, 8.36.120.225, pass
Mon Oct 26 13:27:35 2015 request hub5u.sandai.net
Mon Oct 26 13:27:35 2015 response hub5u.sandai.net from 211.139.29.170:53 - 58.254.134.201, pass
Mon Oct 26 13:27:35 2015 response hub5u.sandai.net from 208.67.222.222:443 - 58.254.134.201, pass

通过源更新到1.3.2后，不能通过非标准端口的上游DNS Server查询DNS记录

dig twitter.com @127.0.0.1 -p 5353

; <<>> DiG 9.9.4 <<>> twitter.com @127.0.0.1 -p 5353
;; global options: +cmd
;; connection timed out; no servers could be reached

chinadns运行一段时间出错了，日志如下

系统环境介绍： openwrt15.05
软件环境：ss开启dns解析，配合chinadns。默认chinadns接管路由器的dns服务

运行一段时间后，所有国外网站打不开：Chroem提示无法显示网页，ERR_NAME_NOT_RESOLVED

以github为例，日志如下：

Mon Nov 9 15:17:39 2015 request github.com
Mon Nov 9 15:17:39 2015 response github.com from 114.114.114.114:53 - 192.30.252.130, filter
Mon Nov 9 15:17:41 2015 request github.com
Mon Nov 9 15:17:42 2015 response github.com from 114.114.114.114:53 - 192.30.252.130, filter
Mon Nov 9 15:17:42 2015 request github.com
Mon Nov 9 15:17:43 2015 response github.com from 114.114.114.114:53 - 192.30.252.130, filter
Mon Nov 9 15:17:43 2015 request github.com
Mon Nov 9 15:17:44 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:45 2015 request github.com
Mon Nov 9 15:17:45 2015 request github.com
Mon Nov 9 15:17:46 2015 response github.com from 114.114.114.114:53 - 192.30.252.131, filter
Mon Nov 9 15:17:46 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:47 2015 request github.com
Mon Nov 9 15:17:48 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:48 2015 request github.com
Mon Nov 9 15:17:49 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:49 2015 request github.com
Mon Nov 9 15:17:49 2015 request github.com
Mon Nov 9 15:17:49 2015 request github.com
Mon Nov 9 15:17:50 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:50 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:50 2015 response github.com from 114.114.114.114:53 - 192.30.252.131, filter
Mon Nov 9 15:17:51 2015 request github.com
Mon Nov 9 15:17:51 2015 request github.com
Mon Nov 9 15:17:52 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:52 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:55 2015 request github.com
Mon Nov 9 15:17:55 2015 request github.com
Mon Nov 9 15:17:56 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:17:56 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:01 2015 request github.com
Mon Nov 9 15:18:01 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:02 2015 request github.com
Mon Nov 9 15:18:02 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:03 2015 request github.com
Mon Nov 9 15:18:03 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:05 2015 request github.com
Mon Nov 9 15:18:05 2015 request github.com
Mon Nov 9 15:18:05 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:05 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:06 2015 request github.com
Mon Nov 9 15:18:06 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:07 2015 request github.com
Mon Nov 9 15:18:07 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:08 2015 request github.com
Mon Nov 9 15:18:08 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:09 2015 request github.com
Mon Nov 9 15:18:09 2015 request github.com
Mon Nov 9 15:18:09 2015 request github.com
Mon Nov 9 15:18:09 2015 response github.com from 114.114.114.114:53 - 192.30.252.130, filter
Mon Nov 9 15:18:09 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:09 2015 response github.com from 114.114.114.114:53 - 192.30.252.129, filter
Mon Nov 9 15:18:11 2015 request github.com
Mon Nov 9 15:18:11 2015 request github.com
Mon Nov 9 15:18:11 2015 response github.com from 114.114.114.114:53 - 192.30.252.129, filter
Mon Nov 9 15:18:11 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:15 2015 request github.com
Mon Nov 9 15:18:15 2015 request github.com
Mon Nov 9 15:18:15 2015 response github.com from 114.114.114.114:53 - 192.30.252.128, filter
Mon Nov 9 15:18:15 2015 response github.com from 114.114.114.114:53 - 192.30.252.131, filter

希望能尽快解决。

pkg_run_script: package "bind-libs" postinst script returned status 127.
opkg_configure: bind-libs.postinst returned 127.