发新话题
打印

我的反向解析申请过程

看看我这个是什么意思????

Reverse DNS for 219.238.233.103
Generated by www.DNSstuff.com
Country: [APNIC Unlisted]

Preparation:
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.
So, the reverse DNS entry for 219.238.233.103 is found by looking up the PTR record for
103.233.238.219.in-addr.arpa.
All DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.

How I am searching:
Asking f.root-servers.net for 103.233.238.219.in-addr.arpa PTR record:
f.root-servers.net says to go to NS1.APNIC.NET. (zone: 219.in-addr.arpa.)
Asking NS1.APNIC.NET. for 103.233.238.219.in-addr.arpa PTR record:
ns1.apnic.net says to go to ns.cnc.ac.cn. (zone: 238.219.in-addr.arpa.)
Asking ns.cnc.ac.cn. for 103.233.238.219.in-addr.arpa PTR record:
ns.cnc.ac.cn says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns1.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns1.datadragon.net says to go to dns2.datadragon.net. (zone: 233.238.219.in-addr.arpa.)
Asking dns2.datadragon.net. for 103.233.238.219.in-addr.arpa PTR record:
dns2.datadragon.net says to go to dns1.datadragon.net. (zone: 233.238.219.in-addr.arpa.)

Error: It looks like you've stuck me in a loop!.

Details:
I am programmed to stop after 20 DNS queries, since most reverse DNS lookups can be finished
after just 3 queries. It sounds like you're stuck in a loop.


To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.




--------------------------------------------------------------------------------

(C) Copyright 2000-2004 R. Scott Perry

TOP

Re:我的反向解析申请过程

深圳电信回复我了,电信目前还没有该服务!;(
呵呵,我是小笨

TOP

Re:我的反向解析申请过程

唉,还要再争取一下,不能发的地方越来越多了
唉,干这行惨哪...... [IMG]http://www.yuhome.cn/other/maomao.jpg[/IMG]

TOP

Re:我的反向解析申请过程

哎,帮顶

TOP

Re:我的反向解析申请过程

广东的同志们快去找他们啊,我已经做成了,是省局给做的反向解析。

TOP

re:我的这个什么意思?有戏吗?另外,我自...

我的这个什么意思?有戏吗?
另外,我自己在内网搞了一个dns,解释内网的ip,能把外网也做进来吗?

Reverse DNS for 221.136.81.89
Generated by www.DNSstuff.com
Country: CHINA

Preparation:
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.
So, the reverse DNS entry for 221.136.81.89 is found by looking up the PTR record for
89.81.136.221.in-addr.arpa.
All DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.

How I am searching:
Asking d.root-servers.net for 89.81.136.221.in-addr.arpa PTR record:
d.root-servers.net says to go to NS4.APNIC.NET. (zone: 221.in-addr.arpa.)
Asking NS4.APNIC.NET. for 89.81.136.221.in-addr.arpa PTR record:
ns4.apnic.net says to go to second1.nbip.com. (zone: 136.221.in-addr.arpa.)
Asking second1.nbip.com. for 89.81.136.221.in-addr.arpa PTR record: Reports that no PTR records exist.

Answer:
No PTR records exist for 221.136.81.89. [Neg TTL=3600 seconds]

Details:
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)
says that there are no PTR records for 221.136.81.89.

To get reverse DNS set up for 221.136.81.89, you need to speak to your Internet provider. You could also
check with admin@nbip.net., who is in charge of the 136.221.in-addr.arpa. zone.

Note that all Internet accessible hosts are expected to have a reverse DNS entry (per RFC1912 2.1),
and many mailservers (such as AOL) will likely block E-mail from mailservers with no reverse DNS entry.
To see the reverse DNS traversal, to make sure that all DNS servers are reporting the correct results, you can Click Here.


TOP

re:我的使用中国网通。一通电话,立马解决。

我的使用中国网通。一通电话,立马解决。

TOP

re:我用的是联通的,也是给个电话就给我搞定了...

我用的是联通的,也是给个电话就给我搞定了,哈。。谁叫我们是联通的大客户呢,我们的电话也是用们的

TOP

re:d

d

TOP

re:我们的是中企网给做解析,tmd也是说我们...

我们的是中企网给做解析,tmd也是说我们不提供反向解析服务,我考tmd,去岁我了

TOP

发新话题
  清除 Cookies - 联系我们 - 邮件技术资讯网 - Archiver - WAP - 繁體中文
当前时区 GMT+8, 现在时间是 2008-10-11 10:08

本论坛为非盈利中立机构,论坛所有言论纯属发表者个人意见,与《 邮件技术资讯网》论坛立场无关。内容所涉及的版权和法律相关事宜请参考各自所有者的条款。
如果认定侵犯了您的权利,请联系我们尽快处理。本论坛原创内容请联系本站后再行转载并务必保留我站信息。此声明修改不再另行通知,本论坛保留最终解释权。
*本论坛QQ群:1#群2233231(已满) 2#群2598254(推荐) 3#群15974064(推荐) 4#群14173252(推荐)*
* 建议使用 1024×768 模式查看本论坛 *
Powered by Discuz! 6.1.0