Searching for unalesto.com A record at m.root-servers.net [202.12.27.33]: Got referral to B.GTLD-SERVERS.NET. (zone: com.) [took 205 ms]
Searching for unalesto.com A record at B.GTLD-SERVERS.NET. [192.33.14.30]: Got referral to ns2.mydnsfake.com. (zone: unalesto.com.) [took 231 ms]
Searching for unalesto.com A record at ns2.mydnsfake.com. [163.30.85.25]: Reports unalesto.com. [took 220 ms]
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 203.87.155.69 is found by looking up the PTR record for
69.155.87.203.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 g.root-servers.net for 69.155.87.203.in-addr.arpa PTR record:
g.root-servers.net says to go to tinnie.arin.net. (zone: 203.in-addr.arpa.)
Asking tinnie.arin.net. for 69.155.87.203.in-addr.arpa PTR record: Timed out [at 199.43.0.195]. Trying again.
Asking ns4.apnic.net. for 69.155.87.203.in-addr.arpa PTR record:
ns4.apnic.net [202.12.31.140] says to go to dns1.meridiantelekoms.com. (zone: 155.87.203.in-addr.arpa.)
Asking dns1.meridiantelekoms.com. for 69.155.87.203.in-addr.arpa PTR record: Reports that no PTR records exist [from 203.87.128.3].
Comment