看看我这个是什么意思？？？？
Reverse DNS for 219.238.233.103<br>Generated by www.DNSstuff.com<br>
Country: [APNIC Unlisted]<br>
<br>
Preparation:<br>
The reverse DNS entry for an IP is found by reversing the IP, adding it to "in-addr.arpa", and looking up the PTR record.<br>
So, the reverse DNS entry for 219.238.233.103 is found by looking up the PTR record for<br>103.233.238.219.in-addr.arpa.<br>
All DNS requests start by asking the root servers, and they let us know what to do next.<br>
See How Reverse DNS Lookups Work for more information.<br>
<br>
How I am searching:<br>
Asking f.root-servers.net for 103.233.238.219.in-addr.arpa PTR record: <br>f.root-servers.net says to go to NS1.APNIC.NET. (zone: 219.in-addr.arpa.)<br>
Asking NS1.APNIC.NET. for 103.233.238.219.in-addr.arpa PTR record: <br>ns1.apnic.net says to go to ns.cnc.ac.cn. (zone: 238.219.in-addr.arpa.)<br>
Asking ns.cnc.ac.cn. for 103.233.238.219.in-addr.arpa PTR record: <br>ns.cnc.ac.cn says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record: <br>dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)<br>
<br>
Error: It looks like you've stuck me in a loop!.<br>
<br>
Details:<br>
I am programmed to stop after 20 DNS queries, since most reverse DNS lookups can be finished<br>
after just 3 queries. It sounds like you're stuck in a loop.<br>
<br>
<br>
To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.<br>
<br>
<br>
<br>
<br>
--------------------------------------------------------------------------------<br>
<br>
(C) Copyright 2000-2004 R. Scott Perry
Re:我的反向解析申请过程
深圳电信回复我了，电信目前还没有该服务！；（Re:我的反向解析申请过程
唉，还要再争取一下，不能发的地方越来越多了Re:我的反向解析申请过程
哎，帮顶Re:我的反向解析申请过程
广东的同志们快去找他们啊，我已经做成了，是省局给做的反向解析。re:我的这个什么意思？有戏吗？另外，我自...
我的这个什么意思？有戏吗？<br>另外，我自己在内网搞了一个dns，解释内网的ip，能把外网也做进来吗？<br>
<br>
Reverse DNS for 221.136.81.89<br>
Generated by www.DNSstuff.com<br>
Country: CHINA<br>
<br>
Preparation:<br>
The reverse DNS entry for an IP is found by reversing the IP, adding it to "in-addr.arpa", and looking up the PTR record.<br>
So, the reverse DNS entry for 221.136.81.89 is found by looking up the PTR record for<br>89.81.136.221.in-addr.arpa.<br>
All DNS requests start by asking the root servers, and they let us know what to do next.<br>
See How Reverse DNS Lookups Work for more information.<br>
<br>
How I am searching:<br>
Asking d.root-servers.net for 89.81.136.221.in-addr.arpa PTR record: <br>d.root-servers.net says to go to NS4.APNIC.NET. (zone: 221.in-addr.arpa.)<br>
Asking NS4.APNIC.NET. for 89.81.136.221.in-addr.arpa PTR record: <br>ns4.apnic.net says to go to second1.nbip.com. (zone: 136.221.in-addr.arpa.)<br>
Asking second1.nbip.com. for 89.81.136.221.in-addr.arpa PTR record: Reports that no PTR records exist.<br>
<br>
Answer:<br>
No PTR records exist for 221.136.81.89. [Neg TTL=3600 seconds]<br>
<br>
Details:<br>
second1.nbip.com. (an authoritative nameserver for 136.221.in-addr.arpa., which is in charge of the reverse DNS for 221.136.81.89)<br>
says that there are no PTR records for 221.136.81.89.<br>
<br>
To get reverse DNS set up for 221.136.81.89, you need to speak to your Internet provider. You could also<br>
check with admin@nbip.net., who is in charge of the 136.221.in-addr.arpa. zone.<br>
<br>
Note that all Internet accessible hosts are expected to have a reverse DNS entry (per RFC1912 2.1),<br>
and many mailservers (such as AOL) will likely block E-mail from mailservers with no reverse DNS entry.<br>
To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.<br>
<br>
<br>
re:我的使用中国网通。一通电话，立马解决。
我的使用中国网通。一通电话，立马解决。re:我用的是联通的，也是给个电话就给我搞定了...
我用的是联通的，也是给个电话就给我搞定了，哈。。谁叫我们是联通的大客户呢,我们的电话也是用们的re:d
dre:我们的是中企网给做解析，tmd也是说我们...
我们的是中企网给做解析，tmd也是说我们不提供反向解析服务，我考tmd，去岁我了<br>re:说的是不是IP反向解析，是不是和域名反向...
说的是不是IP反向解析，是不是和域名反向解析两码事？<br><br>
我是浙江金华的，我们的IP是金华电信提供的，我查了一下我们的邮件服务器IP也没有反向解析！而且也被列入了一些黑名单，我应该找谁？浙江有人做过吗？
偶的反向是ISP提供的，我们用的网通，本来我也不知道要做这个，但是发到AOL的信总
re:如此说来反向解析也是通过层层授权...
如此说来<br>反向解析也是通过层层授权<br>
最后还是在一台DNS服务器上做的PTR记录?<br>
再如此说来<br>
域名提供商如果没有授权管理该段IP地址的话即使设了PTR记录也没什么用?
re:有没有人在东莞做反向解析,要找谁才可以做...
有没有人在东莞做反向解析,要找谁才可以做呢.感激啊!!!re:偶是东莞的~~~以前的公司也是南凌科...
偶是东莞的~~~<br>以前的公司也是南凌科技(东莞)负责，找那里的人渣好了~~~