200.253.177.130

---------- Forwarded message ----------
From: David Farias <[email protected]>
Date: Sep 22, 2005 2:20 PM
Subject: My Server is Still in Black List.
To: [email protected]

 Good Morning.

Dns reverse is configured in my server, and still I continue in the list.

What I must make?

  Location <http://www.dnsstuff.com/info/geolocation.htm>: Brazil
[City: Teresina, Piauí]




*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 200.253.177.130
<http://200.253.177.130/> is found by looking up the PTR record for

 130.177.253.200.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 <http://www.dnsstuff.com/info/revdns.htm>
for more information.



*How I am searching*:

Asking
i.root-servers.net <http://i.root-servers.net/> for
130.177.253.200.in-addr.arpa PTR record:

       i.root-servers.net <http://i.root-servers.net/> says to go to
tinnie.arin.net <http://tinnie.arin.net/>. (zone: 200.in-addr.arpa.)

Asking
tinnie.arin.net <http://tinnie.arin.net/>. for
130.177.253.200.in-addr.arpa PTR record:

       tinnie.arin.net <http://tinnie.arin.net/> [69.25.34.195
<http://69.25.34.195/>] says to go to A.DNS.BR <http://a.dns.br/>.
(zone: 253.200.in-addr.arpa.)


Asking A.DNS.BR <http://a.dns.br/>. for 130.177.253.200.in-addr.arpa
PTR record:


a.dns.br <http://a.dns.br/> [200.160.0.10 <http://200.160.0.10/>] says
to go to ns2.embratel.net.BR <http://ns2.embratel.net.br/>. (zone:
177.253.200.in-addr.arpa.)

Asking ns2.embratel.net.BR <http://ns2.embratel.net.br/>. for
130.177.253.200.in-addr.arpa PTR record:  Got CNAME referral (with no
NS) to
h.root-servers.net <http://h.root-servers.net/> (zone
130.128-191.177.253.200.in-addr.arpa.) [from 200.245.255.33
<http://200.245.255.33/>]


Asking h.root-servers.net <http://h.root-servers.net/> for
130.128-191.177.253.200.in-addr.arpa. PTR record:


       h.root-servers.net <http://h.root-servers.net/> [128.63.2.53
<http://128.63.2.53/>] says to go to ns-sec.ripe.net
<http://ns-sec.ripe.net/>. (zone: 200.in-addr.arpa.)

Asking ns-sec.ripe.net <http://ns-sec.ripe.net/>. for
130.128-191.177.253.200.in-addr.arpa. PTR record:

       ns-sec.ripe.net <http://ns-sec.ripe.net/> [193.0.0.196
<http://193.0.0.196/>] says to go to
E.DNS.BR <http://e.dns.br/>. (zone: 253.200.in-addr.arpa.)

Asking E.DNS.BR <http://e.dns.br/>. for 130.128-191.177.253.200.in-addr.arpa
. PTR record:

       e.dns.br <http://e.dns.br/> [139.91.1.20 <http://139.91.1.20/>]
says to go to ns.embratel.net.BR <http://ns.embratel.net.br/>. (zone:
177.253.200.in-addr.arpa.)

Asking
ns.embratel.net.BR <http://ns.embratel.net.br/>. for
130.128-191.177.253.200.in-addr.arpa. PTR record:  Got NODATA response
type 2 [from 200.255.253.241 <http://200.255.253.241/>].



*Answer*:

There is no PTR record for 130.128-191.177.253.200.in-addr.arpa. (but
130.128-191.177.253.200.in-addr.arpa. is valid).