据百度内部人士透露，百度网络交易平台中文名和域名已经确定。中文名为“有啊”，目前仍然未正式上线。以下是网友的评论：
哈哈 简直笑抽了…… 百度，有了啊！
全称是“啥都没有啊”
有码吗？ 有啊！ 那不要了
有三聚氰胺么？ 有啊
有小姐吗？有啊
有病吗？百度回答：“有啊！ ”
今天百度了么？没“有啊”
据传百度接下来的配套项目分别是：百度缺呀，百度2呀
A：东西不错嘛，哪里买的呀？ B：网上，有啊 A：我知道网上有，具体是哪个网站？ B：有啊 A：我知道有，可是到底是哪里啊 B：靠，百度的淘宝
A：我想买本书. B：百度有啊！ A：百度哪里有？ B：百度有啊有啊！ A：百度哪里有啊？ B：百度有啊有啊！
10月8日消息，据百度内部人士透露，百度网络交易平台中文名和域名已经确定。中文名为“有啊”，域名为youa.com，目前仍然未正式上线。
因为此前获得了百度C2C平台的内测名额，刚才正式收到百度短信通知如下：“尊敬的商户，百度网络交易平台现已正式命名“百度有啊”，开业在即如果您的店铺至今还未启用，请尽快认证激活。百度有啊”
此图为百度平台刚发来的消息
9月25日,中国音乐著作权协会发起抵制网络盗版音乐的行动.要求所有与音乐相关的厂商停止与百度合作.同一天,世界电子巨头LG宣布拒绝在百度MP3投放任何形式的广告,他们将不再为盗版买单.
据悉,LG是互联网公司的顶级客户,每年广告订单在千万数量级.继LG之后,诺基亚等其他顶级客户也正在考虑停止对百度的广告投放,百度面临着巨大的财务危机.
品牌广告主拒绝百度
LG撤离百度是“品牌广告主拒绝百度”行动获得的首战告捷.这一行动是在今年6 月,由中国音像著作权集体管理协会(CAVCA)和国际唱片业协会(IFPI)以及环球、华纳、Sony BMG、百代、福茂、太麦、种子、竹书、源泉等主要华语唱片及其版权公司发起的.
这一联盟代表了国内、国际最主要的音乐机构,他们联合起来抵制百度,并且倡议广告主和广告客户爱惜自身品牌形象,不助长盗版等有害社会的行为,拒绝在百度做任何形式的广告投放.
行动很快受到著名品牌厂商的高度关注.LG表示:“LG非常重视广告和市场活动的品牌形象以及各种广告素材的版权保护,从2008年8月1日起,LG将不会在mp3.baidu.com上投放任何形式的广告.”
中国音乐著作权协会总干事屈景明对LG的做法表示赞赏,他说:“百度是中国最大的数字音乐盗版源头,这已经成为了音乐界乃至全社会的共识.百度依靠盗版等 非法手段牟取巨大流量,并以此交换巨额广告收益.所以,任何在百度投放广告的行为都是对盗版的间接支持.作为拥有巨大品牌价值的LG拒绝在百度投放广告, 既是对自身品牌价值的保护,也是对全体音乐界的尊重,更是为诚信经商的表率.”据介绍,除LG之外,已有多家知名品牌公司已向音乐界表达了抵制盗版媒体的 共识,随着“品牌广告主拒绝百度”行动的深入,将会有越来越多的品牌厂商站出来,拒绝在百度投放广告.
以搜索之名 行盗版之实
LG方面解释,他们以前在百度MP3投放广告是因为他们一直以为这是一项搜索业务,并没有盗版问题.直到他们看到音乐版权管理公司源泉公司的分析报告之后 才知道,原来百度一直借搜索之名,行盗版之实,所以他们果断做出停止投放广告的决定.源泉CEO吴峻说,作为一个中立的技术搜索引擎,音乐搜索的主要结果 应该来自音乐和综合类网站以及BBS、博客等互动类网站,但是他们从2007年下半年开始用600多首歌曲在百度上定期搜索发现,大量的搜索结果另有出 处.
在源泉的搜索监测中,经常出现一个域名为www.zpeb.net的网站,其曲库量大约在前30名左右.按照正常推断,这一定是一个音乐类网站,事实它却 是某石油勘探局的网站.而且,用户正常登录这个网站,是无法找到任何音乐内容的.除此之外,源泉还发现“YY系列”的神秘网站,这个系列中的域名都是以一 个英文字母加一个阿拉伯数字加字母“yy”组成的,这些网站无法访问,但百度却能经常“搜索”到它们服务器中存储的音乐内容.
文/新华网
百度日本分公司近日正式启用了Baidu.co.jp域名与Baidu.jp 共同提供搜索服务（中国大陆暂无法访问）。
在此之前，百度日本曾因Baidu.co.jp域名问题与该域名之前的所有者交涉，随后获得了日本政府获胜裁定，但由于一些原因，裁定后就一直没有了消 息。据记者获悉，百度日本自2008年7月10号正式获得了Baidu.co.jp域名的非物质财产所有权，自 7月31日正式启用。
百度今日宣布任命井上俊一为百度日本总裁，此任命从宣布之日起正式生效。
“井上先生在日本具有长达10年从事互联网搜索业务的经历，不仅深刻了解日本互联网和搜索引擎市场的发展状况，而且拥有广阔的国际化视野和丰富的国际化企业管理经验。他的技术和产品经验，必将为百度日本带来新的活力。”百度董事会主席兼首席执行官李彦宏表示。
井上先生1998年起在著名搜索引擎Excite日本担任首席技术官，2004年加入雅虎日本，历任搜索事业部部长、主管搜索业务的副总裁，负责雅虎日本所有的搜索产品，为雅虎在日本市场上成为市场占有率最高的搜索引擎做出了重要贡献。
“作为日本互联网搜索产业的领军人物，井上先生的加盟是百度日本业务发展迄今为止最重要的里程碑事件，极大增强了百度在日本市场上吸引更多一 流人才、提供更好的产品与服务的信心，也必将促进百度日本各项业务得到更加迅猛的发展。”百度负责国际业务的市场和商务拓展副总裁任旭阳表示。
此次Baidu.co.jp域名的正式启用更符合日本国民的日常习惯，将极大的对百度在日本市场的推进产生积极影响。日前刚有消息称百度日本总裁人选将浮出水面。记者对百度日本近日的诸多动作将保持高度关注。
新闻来源:新浪科技
百度今日凌晨在公司内部公布了IM产品内测通知。根据该通知，百度IM产品名字已敲定为“百度Hi”。另据消息人士透露，百度公司计划于29日上午正式展开该产品的全员内测。
据悉，百度北京总部今日凌晨悄然在公司门口摆出了“百度Hi”内测通知的易拉宝，以在天亮后吸引上班同事的目光。该易拉宝上面的内容是：百度Hi有奖抢“鲜”体验，请访问app.im.baidu.com。截稿前，该网址仍无法访问，其端口或只向百度内部员工开放。
“百度Hi”的首个LOGO（文雄 摄）
百度公司门口摆放的“百度Hi”内测宣传易拉宝（文雄 摄）
百度Hi登录界面
在此之前，外界关于百度IM的最新消息是，百度IM产品中文名字暂定为“百度 Hi”。而今日上午，新浪科技曾获悉一张百度IM截图。从截图上看，百度IM软件名叫“Baidu Messenger”，并不是之前网友热传的“百度小声”或者“百度说吧”。
不过，百度官方当时未就该图片与名字发表评论。有内部人士对此指出，该界面是百度IM产品测试期间的一个版本，Baidu Messenger的名字也是暂定，最终名字与软件界面有望在下周敲定。
百度有意推IM产品的传闻由来已久，近期在其官网最新公布的招聘页面中，百度已向外界罗列出即时通信客户端软件研发工程师(搜索新产品研发部)、即时通信软件产品经理(客户端软件业务部)等职位，上述工作地点均在北京，百度IM战略布局初具雏形。
随后，新浪科技获悉一封百度公司内部邮件，该邮件面向全体员工征集对公司做IM(即时通信软件)的意见和看法。这是继宣布招聘IM研发人才之后，百度在IM领域的又一重要进展。
值得注意的是，百度CEO李彦宏此前也对外界风传百度将做IM的消息保持高度关注，他曾评论说“百度小声是个不错的名字，我喜欢，就是不知道是谁的创意。”上述“百度小声”正是百度IM名字的一个传说版本。
有相关人士表示，百度曾考虑过“百度小声”、“百度说吧”、“百度Hi”等中文名字，最终带有百度空间“Hi”印记的后者在内部获得较高支持率。实际上，百度对IM产品的定位也正是为满足其社区用户需求。
业内人士认为，百度去年宣布将进入C2C市场，已引起阿里巴巴方面的高度关注。如果百度大举踏入IM市场，未来难免在市场中正面遭遇腾讯，IM市场的格局也因此添加几分不确定性。
据消息人士透露,百度即将正式推出的即时通讯工具定名为“百度 Hi”,目前百度已开始着手宣传准备工作.
今天上午曾有媒体公布了一张“百度IM截图”,并称该百度IM软件名称为“Baidu Messenger”.但该消息人士称,百度的IM软件并非“Baidu Messenger”,而是叫“百度 Hi”,而网上公布的所谓截图也不一定就是真正的百度IM工具正式界面.
近日,百度推出IM产品的相关传闻甚嚣尘上.在百度官方网站公布的招聘信息里曾经列出“即时通信户端软件研发工程师”等相关职位;近日还有消息称,百度已向部分员工发放了一份《抢先体验IM的内部问卷》,更是显示了其市场部署已进入实质阶段.
此前,网友和业内人士对于百度IM软件的名称也有着“百度小声”、“百度说吧”等等多种猜测.
网易科技消息
一直以来,百度公司及其掌门人李彦宏很少在国内谈及百度开拓日本搜索市场的详细情况.日前,李彦宏本人接受了日本媒体的采访,他第一次深度谈及百度日文的 战略发展.其间,李彦宏称Google在中国假装成一家中国公司,他说中国媒体曾被百度日文版的预告广告“忽悠”.李彦宏还说,百度并不是一个纯粹的中国 公司,但也“不完全是”一个总部在北京的跨国公司.以下是采访集锦:
问:为什么选择日本作为百度的第一个海外市场?
1、 Sina.com.cn
http://www.dnsstuff.com/tools/dnsreport.ch?domain=sina.com.cn
Parent
INFO NS records at parent serversYour NS records at the parent servers are: ns2.sina.com.cn. [61.172.201.254 ] [TTL=21600] [CN]
ns3.sina.com.cn . [202.108.44.55] [TTL=21600] [CN]
ns1.sina.com.cn. [202.106.184.166] [TTL=21600] [CN]
[These were obtained from cns.cernet.net]
NS INFO Nameservers versions Your nameservers have the following versions: 61.172.201.254: No version info available (refused).
202.108.44.55: No version info available (refused).
202.106.184.166: No version info available (refused).
SOA
WARN SOA Serial NumberWARNING: Your SOA serial number is: 5. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where ‘nn’ is the revision. For example, if you are making the 3rd change on 02 May 2006, you would use 2006050203. This number must be incremented every time you make a DNS change.
WARN SOA MINIMUM TTL valueWARNING: Your SOA MINIMUM TTL is : 600 seconds. This seems low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
规范等级：中
http://www.dnsstuff.com/tools/dnsreport.ch?domain=sina.com
Parent
INFO NS records at parent serversYour NS records at the parent servers are: ns1.sina.com.cn. [ 202.106.184.166 (NO GLUE)] [CN]
ns2.sina.com.cn. [61.172.201.254 (NO GLUE)] [CN]
ns3.sina.com.cn. [202.108.44.55 (NO GLUE)] [CN]
[These were obtained from l.gtld-servers.net]
WARN Glue at parent nameservers
WARNING. The parent servers (I checked with l.gtld-servers.net.) are not providing glue for all your nameservers. This means that they are supplying the NS records ( host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of ” ns1.example.org” for the domain “example.com“). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.
NS
WARN Nameservers on separate class C’s
WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
INFO Nameservers versionsYour nameservers have the following versions: 202.106.184.166: No version info available (refused).
61.172.201.254 : No version info available (refused).
202.108.44.55: No version info available (refused).
WARN Nameservers on separate class C’s
WARNING: We cannot test to see if your nameservers are all on the same Class C (technically, /24) range, because the root servers are not sending glue. We plan to add such a test later, but today you will have to manually check to make sure that they are on separate Class C ranges. Your nameservers should be at geographically dispersed locations. You should not have all of your nameservers at the same location. RFC2182 3.1 goes into more detail about secondary nameserver location.
SOA WARN SOA MNAME Check
WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: sina.com. . However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.
WARN SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 900 seconds. This seems low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
WARN SOA MINIMUM TTL value
WARNING: Your SOA MINIMUM TTL is : 300 seconds. This seems low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
规范等级：低
2、 sohu.com
http://www.dnsstuff.com/tools/dnsreport.ch?domain=sohu.com
Parent
INFONS records at parent serversYour NS records at the parent servers are:dns.sohu.com. [61.135.131.86] [TTL=172800] [CN]
ns1.sohu.com. [61.135.131.1] [TTL=172800] [CN]
ns3.sohu.com. [220.181.26.168] [TTL=172800] [CN]
[These were obtained from a.gtld-servers.net]
NS
WARN Single Point of Failure
WARNING: Although you have at least 2 NS records, and they appear to point to different physical servers, it appears that they block the ICMP packets used as part of our test, which means that they may share the same firewall. If they share the same firewall, this results in a single point of failure, which could cause all your DNS servers to be unreachable.
INFO Nameservers versionsYour nameservers have the following versions:61.135.131.86: ” ”
61.135.131.1: ” ”
220.181.26.168: ” ”
SOA
FAILSOA MINIMUM TTL value
WARNING: Your SOA MINIMUM TTL is : 60 seconds. This seems very low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
规范等级：高
3、163.com
http://www.dnsstuff.com/tools/dnsreport.ch?domain=163.com
Parent
INFO NS records at parent serversYour NS records at the parent servers are:ns.nease.net. [202.106.185.75] [TTL=172800] [CN]
ns3.nease.net. [220.181.28.3] [TTL=172800] [CN]
[These were obtained from a.gtld-servers.net ]
NS
INFO Nameservers versions Your nameservers have the following versions: 202.106.185.75: “9.2.3”
220.181.28.3: “9.2.3”
SOA
FAILNS agreement on SOA Serial #
ERROR: Your nameservers disagree as to which version of your DNS is the latest (20011937 versus 20011938). This is OK if you have just made a change recently, and your secondary DNS servers haven’t yet received the new information from the master. I will continue the report, assuming that 20011938 is the correct serial #. The serial numbers reported by each DNS server are:
202.106.185.75: 20011938
220.181.28.3: 20011937
WARN SOA Serial Number
WARNING: Your SOA serial number is: 20011938. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where ‘nn’ is the revision. For example, if you are making the 3rd change on 02 May 2006, you would use 2006050203. This number must be incremented every time you make a DNS change.
规范等级：中
http://www.dnsstuff.com/tools/dnsreport.ch?domain=nease.net
Parent
INFO NS records at parent serversYour NS records at the parent servers are: ns.nease.net. [202.106.185.75] [TTL=172800] [CN]
ns3.nease.net. [220.181.28.3] [TTL=172800] [CN]
[These were obtained from j.gtld-servers.net]
NS
INFO Nameservers versions Your nameservers have the following versions: 202.106.185.75: “9.2.3”
220.181.28.3: “9.2.3”
SOA
WARN SOA Serial Number
WARNING: Your SOA serial number is: 991160. That is OK, but the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where ‘nn’ is the revision. For example, if you are making the 3rd change on 02 May 2006, you would use 2006050203. This number must be incremented every time you make a DNS change.
WARN SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can’t reach the primary nameserver.
规范等级：中
4、 tom.com
http://www.dnsstuff.com/tools/dnsreport.ch?domain=tom.com
Parent
INFO NS records at parent serversYour NS records at the parent servers are: brown.hutchcity.com. [202.45.84.67] [TTL=172800] [HK]
edns.wyith.net. [202.181.240.44] [TTL=172800] [HK]
ns1.tom.com. [61.135.159.46] [TTL=172800] [CN]
ns2.tom.com. [61.135.159.47] [TTL=172800] [CN]
[These were obtained from f.gtld-servers.net ]
NS
FAILOpen DNS servers
ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn’t happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are: Server 202.45.84.67 reports that it will do recursive lookups. [ test] Server 202.181.240.44 reports that it will do recursive lookups. [ test] Server 61.135.159.46 reports that it will do recursive lookups. [ test] Server 61.135.159.47 reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers.
FAIL Lame nameservers
ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
202.45.84.67
FAIL Missing nameservers 2
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
brown.hutchcity.com.
edns.wyith.net.
WARN All nameservers report identical NS records
WARNING: Your nameservers report somewhat different answers for your NS records (varying TTL, for example).
INFO Nameservers versions Your nameservers have the following versions: 202.45.84.67: “8.3.4-REL”
202.181.240.44: “4.9.6-REL”
61.135.159.46: “TOM.COM DNS Server 2.00″
61.135.159.47 : “TOM.COM DNS Server 2.00″
规范等级：低
5、qq.com
http://www.dnsstuff.com/tools/dnsreport.ch?domain=qq.com
Parent
INFO NS records at parent serversYour NS records at the parent servers are:dns1.imok.net. [219.133.40.202] [TTL=172800] [CN]
dns2.imok.net. [61.152.100.5] [TTL=172800] [CN]
[These were obtained from e.gtld-servers.net ]
NS
WARN Single Point of Failure
WARNING: Although you have at least 2 NS records, there is a chance that they may both point to the same server (one of our two tests shows them being different, the other is unsure; it appears that there are one or more firewall(s) that intercept and alter DNS packets (some versions of Linux reportedly have a built-in firewall that does this, too)), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
INFO Nameservers versions Your nameservers have the following versions: 219.133.40.202: “9.3.2”
61.152.100.5: “9.3.0rc4”
SOA
WARN SOA MNAME Check
WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: qq.com.. However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.
WARN SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 300 seconds. This seems low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
WARN SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 86400 seconds. This seems a bit low. You should consider increasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can’t reach the primary nameserver.
规范等级：低
http://www.dnsstuff.com/tools/dnsreport.ch?domain=imok.net
Parent
INFO NS records at parent serversYour NS records at the parent servers are:dns1.imok.net. [219.133.40.202] [TTL=172800] [CN]
dns2.imok.net. [61.152.100.5] [TTL=172800] [CN]
[These were obtained from j.gtld-servers.net ]
NS
WARN Single Point of Failure
WARNING: Although you have at least 2 NS records, there is a chance that they may both point to the same server (one of our two tests shows them being different, the other is unsure; it appears that there are one or more firewall(s) that intercept and alter DNS packets (some versions of Linux reportedly have a built-in firewall that does this, too)), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
INFO Nameservers versions Your nameservers have the following versions: 219.133.40.202: “9.3.2”
61.152.100.5: “9.3.0rc4”
SOA
WARN SOA MNAME Check
WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: imok.net. . However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.
WARN SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 360 seconds. This seems low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
WARN SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 3600000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can’t reach the primary nameserver.
规范等级：低
6、 baidu.com
http://www.dnsstuff.com/tools/dnsreport.ch?domain=baidu.com
Parent
INFONS records at parent serversYour NS records at the parent servers are:dns.baidu.com. [202.108.250.228] [TTL=172800] [CN]
ns2.baidu.com. [202.108.249.147] [TTL=172800] [CN]
ns3.baidu.com. [220.181.27.61] [TTL=172800] [CN]
ns4.baidu.com. [220.181.27.62] [TTL=172800] [CN]
[These were obtained from m.gtld-servers.net]
NS
FAIL Missing (stealth) nameservers
FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly. ns1.baidu.com.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
WARN TCP Allowed
WARNING: One or more of your DNS servers does not accept TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. The problem servers are: 202.108.249.147: Error [No response to TCP packets].
220.181.27.61: Error [No response to TCP packets]. 220.181.27.62: Error [No response to TCP packets].
WARN Single Point of Failure
WARNING: Although you have at least 2 NS records, there is a chance that they may both point to the same server (one of our two tests shows them being different, the other is unsure; it appears that there are one or more firewall(s) that intercept and alter DNS packets (some versions of Linux reportedly have a built-in firewall that does this, too)), which would result in a single point of failure. You are required to have at least 2 nameservers per RFC 1035 section 2.2.
INFO Nameservers versions Your nameservers have the following versions: 202.108.250.228: “diy by bind”
202.108.249.147: “9.2.1 ”
220.181.27.61: “9.2.1”
220.181.27.62: “9.2.1”
FAIL Stealth NS record leakage
Your DNS servers leak stealth information in non-NS requests:
Stealth nameservers are leaked [ns1.baidu.com.]!This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.
SOA
WARN SOA REFRESH value
WARNING: Your SOA REFRESH interval is : 300 seconds. This seems low. You should consider increasing this value to about 3600-7200 seconds. RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours). A value that is too low will unncessarily increase Internet traffic.
WARN SOA EXPIRE value
WARNING: Your SOA EXPIRE time is : 2592000 seconds. This seems a bit high. You should consider decreasing this value to about 1209600 to 2419200 seconds (2 to 4 weeks). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can’t reach the primary nameserver.
规范等级：中
7、 google.com
http://www.dnsstuff.com/tools/dnsreport.ch?domain=google.com
Parent
INFO NS records at parent servers Your NS records at the parent servers are: ns1.google.com. [216.239.32.10] [TTL=172800] [US]
ns2.google.com. [216.239.34.10 ] [TTL=172800] [US]
ns3.google.com. [ 216.239.36.10] [TTL=172800] [US]
ns4.google.com . [216.239.38.10] [TTL=172800] [US]
[These were obtained from k.gtld-servers.net]
NS
INFO Nameservers versions Your nameservers have the following versions: 216.239.32.10: No version info available (refused).
216.239.34.10: No version info available (refused).
216.239.36.10: No version info available (refused).
216.239.38.10: No version info available (refused).
SOA
FAILSOA MINIMUM TTL value
WARNING: Your SOA MINIMUM TTL is : 60 seconds. This seems very low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
规范等级：中
据外国媒体10月18日报道，中国最受欢迎的互联网搜索网站百度公
百度凭借其在中国位于谷歌之上的领导地位，提高利润并且将股价推进
据市场研究公司Analysys International称，第二季度百度在中国搜索市场的市场
http://www.baidu.com/s?wd=site%3Anet.ru&cl=3
抱歉，没有找到与“site:net.ru” 相关的网页。
猜测是baidu人工封站的结果。但是也有可能是baidu的一个bug