RIPN 个人号很多朋友都有很多，目的就是为了要多个域名，但是其实只要有一个 RIPN 就够了。
在申请域名时，请注意，在申请之前申请一个 Maintainer，然后用这个 Maintainer 做管理帐户，这样就可以申请多个域名了，注意，每个Maintainer最好只管理1-2个域名即可。
如果你怕忘了可以在后面加上序号 01 02 03 等等。
还有，再写介绍时，不要雷同即可。也不要乱写一通。
申请域名不要太过于频繁。还有Maintainer申请是机器通过的，所以你可以先一次性申请多个。
补充：
最好用不同的mail来申请 ripn mnt
还有在申请的时候，是用个人号登陆，然后申请域名时要填入不同的 MNT 帐号
个人理解：
MNT主要是管理RIPN的密码邮箱之类的，
你也可以通过Register new Maintainer来注册新的MNT，
如果注册成功可以用新注册的MNT管理你现用的RIPN，
To change the Maintainer of XXX-ORG-RIPN specify the new Maintainer authorization information such as nic-handle (unique identifier), password and e-mail:
其实申请MNT也很简单的
descr (Maintainer description):
mnt-adm (Administrator of Maintainer): XXX-ORG-RIPN
tech-c (Technical Contact):
upd-to (E-mail addresses for failed requests):
mnt-nfy (E-mail addresses for notifications):
auth (Authorization passwords):
auth (E-mail addresses for authorization):
MNT只是管理米的，不可以注册米
MNT 的邮箱最好不要和你的个人号相同
COM.RU域名已不能申请.已申请的可以续注册.续注册攻略
首先进入
http://www.ripn.net/nic/dns/form/en/
然后在点击“域名”进入更新玉米信息
只需要Update一下就OK了
注意：需要等到RIPN给你发通知信的时候,之后Update才有效的！
非常简单！
可以不用那种发信的方法去续.
以下还有三种方法。
第一种方法，写信update
第二种方法，用***-mnt-ripn号，登陆，点update,即可。，
第三种方法，只要你的NS是有效的，譬如是value-domain,zoneedit.com等的NS，他会自动给你续。
附邮件格式：
邮件格式： 发信给：
ru-dns@ripn.net
action: update
passwd:XXXX
#[DOMAIN TEMPLATE]#
domain:XXXXX
type:CORPORATE
descr:XXXXX
comp-d:XXXXX
admin-o:XXXXX
bill-o:XXXX
nserver:XXXXX
nserver:XXXXX
mnt-by:XXXXX
source: RIPN
#[TEMPLATES END]#
ripn查询
http://www.ripn.net:8080/nic/whois/
关于申请RIPN的FAQ
1.什么是RIPN、什么是RIPN帐号？
RIPN是Russian Institute for Public Networks的英文缩写。其中文意思是：俄罗斯公共网络协会。而RIPN帐号所指的就是通过RIPN申请、并且得到RIPN审核通过的合法用户帐号。
2.为什么我们要申请RIPN帐号？
当然，没有人规定上网必须申请RIPN帐号。但是如果你需要一个稳定的、与.com等后缀没有区别的免费国际域名的话，申请RIPN帐号不失为一个不错的选择。 因为一旦拥有RIPN帐号，就可以随意注册以.com.ru/.net.ru
/.org.ru结尾的顶级国际域名（与.com.cn/.net.cn/.org.cn同级）。其与.com等后缀的域名的唯一区别就是不用钱。
3.要注册.ru域名一定要申请RIPN吗？
就目前来说，似乎没有比申请RIPN帐号更好的方法来注册.ru免费域名。虽然RIPN帐号申请比较困难，但是一旦申请成功，在此RIPN帐号下几乎可以注册无限多个.ru域名（此种说法未经证实）相比之下还是值得的。如果你知道申请.ru域名更好的方法，不妨与大家分享哦。^_^
4.RIPN帐号是不是免费的？
当然，注册RIPN帐号是完全免费的。而且全球任何国家的人都可以注册RIPN帐号。
5..ru结尾的域名是不是免费的？
Sure！只要你拥有RIPN帐号，通过RIPN帐号注册.ru域名，不管注册多少都是免费的。
6.申请RIPN帐号有什么需要注意的吗？
申请RIPN帐号需要注意的还是比较多的。在这里也不一一介绍了，大家如果需要可以看看申请攻略。在这里我只提醒大家一点至关重要的，在申请RIPN帐号时，不管是注册组织帐号还是个人帐号，所填写的信息一定要尽可能的真实，尽量用真实的资料申请。只有这样，通过的几率才会大，才不至于枉费大家填那么久申请表啊。
7.申请.ru域名有什么需要注意的吗？
申请.ru域名时倒没什么需要特别注意的。但是有比较重要的一点大家要记住，在申请域名填写DNS服务器时千万不可以随便填写，更不能乱填。一定要注意填写的DNS是已经可以正常解析此域名的DNS。不然，RIPN是会扣留你申请的域名的，等到DNS可以正常解析之后才会正式开通。
2007年11月30日星期五
2007年11月25日星期日
DDOS attacks
We have for the last 2 hours been experiencing a large ddos attack.We are
working to mitigate this, however for the moment sites may run slower than
usual.As ever, we apologize for the actions of the remote party that is causing
this.
2007年11月23日星期五
2007年11月15日星期四
firewall maintanance.
For a short period today we will be altering our network topology slightly / adding new hardware to the firewalls.This will cause a slight outage (we expect 30 minutes max).We can not give an exact time that this will be occurring, as we will waiting for dc hands time.
2007年11月9日星期五
各大网站域名服务器测评
Sina、sohu、tom、163、baidu、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.
规范等级：中
2007年11月2日星期五
Google 黑板报 -- Google 中国的博客网志: 抄近路上谷歌 — 谷歌最简网址 G.cn 上线
今年4月，曾有传言Google将启用g.cn域名。但经核实，只是传言。但今天，这个传言变成了现实。Google黑板报正式宣布谷歌最简网址G.cn上线。刚才查了一下，g.cn的域名注册信息是：注册人: Google Ireland Holdings域名过期时间: 2012-08-24 17:48可以猜测，g.cn是在2007年8月24日或之前不久被转让给Google的。Google随即续费5年。现在，g.cn已经指向59.151.21.100，属于google.cn的IP(对比，4月是指向60.28.193.150，属于天津网通的IP)。对google中国而言，g.cn显然比google.cn更"本地化"，比对手baidu.com更容易记忆。
Google 黑板报 -- Google 中国的博客网志: 抄近路上谷歌 — 谷歌最简网址 G.cn 上线
Google 黑板报 -- Google 中国的博客网志: 抄近路上谷歌 — 谷歌最简网址 G.cn 上线
订阅：
博文 (Atom)
博文
