Log in is no longer required. RBL Alerts and Domain Doctor are no longer available.
What is this tool?
This test will see if a reverse DNS entry exists for an IP address, and will also show you how the entry is found (the route of DNS servers that is taken), and who to contact to get a reverse DSN entry if none is found. The RFCs say that you should have a reverse DNS entry for every host on the Internet. If a mail server is missing a reverse DNS entry, other mail servers may reject mail from it. It supports IPv6 reverse DNS lookups, too.
How do the results help me?
To get Info about an IP causing problems
To verify that a mail server has a Reverse DNS Entry
To Gather Data about who is visiting your web site
The advanced version features the server field allows you to test the reverse DNS on a new DNS server.
... or, "Almost a Reverse DNS FAQ"Reverse DNS turns an IP address into a hostname -- for example, it might turn 192.0.2.25 into .For your domains, standard DNS (turning a hostname into an IP address, such as turning
into 192.0.2.25) starts with the company (registrar) that you registered your domains with. You let them know what DNS servers are responsible for your domain names, and the registrar sends this information to the root servers (technically, the parent servers for your TLD). Then, anyone in the world can access your domains, and you can send them to any IP addresses you want. You have full control over your domains, and can send people to any IPs (whether or not you have control over those IPs, although you should have permission to send them to IPs that are not yours).Reverse DNS uses a similar method. For your IPs, reverse DNS (turning 192.0.2.25 back into ) starts with your ISP (or whoever told you what your IP addresses are). You let them know what DNS servers are responsible for the reverse DNS entries for your IPs (or, they can enter the reverse DNS entries on their DNS servers), and your ISP gives this information out when their DNS servers get queried for your reverse DNS entries. Then, anyone in the world can look up the reverse DNS entries for your IPs, and you can return any hostnames you want (whether or not you have control over those domains, although you should have permission to point them to hostnames that are not on your domains).So for both standard DNS and reverse DNS, there are two steps: [1] You need DNS servers, and [2] You need to tell the right company (your registrar for standard DNS lookups, or your ISP for reverse DNS lookups) where your DNS servers are located. Without Step 2, nobody will be able to reach your DNS servers.If you can comprehend the above paragraphs (which takes some time), you'll understand the biggest problem that people have with reverse DNS entries. The biggest problem people have is that they have DNS servers that work fine with their domains (standard DNS), they add reverse DNS entries to those servers, and it doesn't work. If you understand the above paragraphs, you'll see the problem: If your ISP doesn't know that you have DNS servers to handle the reverse DNS for your IPs, they won't send that information to the root servers, and nobody will even get to your DNS servers for reverse DNS lookups.Basic Concepts:&&& * Reverse DNS turns 192.0.2.25 into
(an IP address into a host name).&&& * Typical reverse DNS lookup path: DNS resolver =& root servers =& ARIN (North American IP registry) =& Local ISP =& Acme Inc. DNS servers.&&& * Whoever supplies your IP addresses (usually your ISP) MUST either [1] set up your reverse DNS entries on their DNS servers, or [2] "delegate authority" for your reverse DNS entries to your DNS servers.&&& * Reverse DNS entries use a host name with a reversed IP address with ".in-addr.arpa" added to it -- for example, "25.2.0.192.in-addr.arpa" (".ip6.arpa" is used for IPv6 reverse DNS lookups).&&& * Reverse DNS entries are set up with PTR records (whereas standard DNS uses A records), which look like "25.2.0.192.in-addr.arpa. PTR " (whereas standard DNS would look like ". A 192.0.2.25").&&& * All Internet hosts should have a reverse DNS entry (see RFC1912 section 2.1).&&& * Mail servers with no reverse DNS will have a hard time getting mail to certain large ISPs. Very Common Myth:&&& * Myth: If you have a reverse DNS entry listed in your DNS server, you have reverse DNS properly set up.&&&&& Fact: This is often not the case. You need TWO things in order to have your DNS set up properly:&&&&&&&&& o 1. Your DNS servers (or your ISP's) MUST have the reverse DNS entries set up ("25.2.0.192.in-addr.arpa. PTR ").&&&&&&&&& o 2. AND your ISP or bandwidth provider MUST set up the reverse DNS on their end, so that DNS resolvers around the world will know that your DNS servers are the ones to go to when looking up the reverse DNS for your IP addresses. How a reverse DNS lookup is accomplished:&&& * The DNS resolver reverses the IP, and adds it to ".in-addr.arpa" (or ".ip6.arpa" for IPv6 lookups), turning 192.0.2.25 into 25.2.0.192.in-addr.arpa.&&& * The DNS resolver then looks up the PTR record for 25.2.0.192.in-addr.arpa.&&&&&&&&& o The DNS resolver asks the root servers for the PTR record for 25.2.0.192.in-addr.arpa.&&&&&&&&& o The root servers refer the DNS resolver to the DNS servers in charge of the Class A range (192.in-addr.arpa, which covers all IPs that begin with 192).&&&&&&&&& o In almost all cases, the root servers will refer the DNS resolver to a "RIR" ("Regional Internet Registry"). These are the organizations that allocate IPs. In general, ARIN handles North American IPs, APNIC handles Asian-Pacific IPs, and RIPE handles European IPs.&&&&&&&&& o The DNS resolver will ask the ARIN DNS servers for the PTR record for 25.2.0.192.in-addr.arpa.&&&&&&&&& o The ARIN DNS servers will refer the DNS resolver to the DNS servers of the organization that was originally given the IP range. These are usually the DNS servers of your ISP, or their bandwidth provider.&&&&&&&&& o The DNS resolver will ask the ISP's DNS servers for the PTR record for 25.2.0.192.in-addr.arpa.&&&&&&&&& o The ISP's DNS servers will refer the DNS resolver to the organization's DNS servers.&&&&&&&&& o The DNS resolver will ask the organization's DNS servers for the PTR record for 25.2.0.192.in-addr.arpa.&&&&&&&&& o The organization's DNS servers will respond with "".| Mx Lookup
MX LOOKUP - Find the mail exchanger for an hostname
Mails flowing to your domain need to be told where to go. Mx records are solving this problem, telling where to address a specific email on the internet. Each time you send an email you are asking (through your SMTP server) which is the computer that handles emails for the recipient hostname.
Your current ip is
DNSQueries News
29 June 2010
We are waiting to know your needs!
25 November 2009
IE8 users can now be free from annoying popups!
16 October 2009
After more than a month of developement we have just released the new toolbar version!
6 October 2009
Statistics told us that our toolbar have more than 500 active users
14 September 2009
We have just released a new smtp tester version!
11 September 2009
After 24h from the deploy
v2 we have released a few improvements to the interface
10 September 2009
We did it again...
WebPartners访问七牛下载链接出现{&error&:&download token auth failed&}_问答_ThinkSAAS
访问七牛下载链接出现{&error&:&download token auth failed&}
访问七牛下载链接出现{&error&:&download token auth failed&}
根据的指南生成私有文件链接，发现文件名是中文的话生成的private_url用chrome会出现
{"error":"download token auth failed"}
的响应（对比英文文件名是正常的）。
七牛要求所有的链接，文件名必须都是UTF-8编码的，所以看看你的代码吧。
Key必须采用utf-8编码，使用非utf-8编码的资源名访问时会报错。
你在做中文的key的下载凭证的时候，key要做url转义的，参考上面的文档的最后面的说明。
你够幸运,我遇到过,告诉你吧
chrome 尤其是mac系统上的(可能跟系统没啥关系,跟浏览器种类也没关系,反正有的电脑就是这样)
你是用utf-8编码后的url 单击链接后,浏览器会再转一次,有的时候是全部转成大写,有的是全部小写,
例如原/downfile/fileidHHHHHaaaaa.rar?e=&token=******
会被自动转码成/downfile/fileidHHHHHAAAAA.rar?e=&token=********
注意小写aaaaa变成了大写AAAAA,也可能是原来大写变成小写的
这只是举例子,实际情况是对utf-8编码后的中文部分进行转码
自动转码可能说的不准确,但是不管看html里面&a href="***aaa"aaa写的是什么,点击打开就会发现浏览器打开的地址变成AAA了
因为这个问题发现的时间比较久了,所以记得不是很清楚,反正基本就是这样,确认你文件名不包括中文,就不会发生此问题
添加你想要问的问题
PHP开发框架
开发工具/编程工具
服务器环境
ThinkSAAS商业授权：
ThinkSAAS为用户提供有偿个性定制开发服务
ThinkSAAS将为商业授权用户提供二次开发指导和技术支持
让ThinkSAAS更好，把建议拿来。
开发客服微信}