nanog mailing list archives

Re: Tracking down reverse for ip

From: William Pitcock <nenolod () systeminplace net>
Date: Thu, 15 Apr 2010 15:59:19 -0500

On Thu, 2010-04-15 at 15:07 -0500, Dennis Burgess wrote:

I have a customer that has an IP of 12.43.95.126. Currently, I can not
get any reverse on this IP.  

 

What is the best way to find out the responciable servers for this?
Thanx in advance.


nenolod@petrie:~$ dig -x 12.43.95.126 +trace @4.2.2.1
; <<>> DiG 9.6.1-P2 <<>> -x 12.43.95.126 +trace @4.2.2.1
;; global options: +cmd
.                       26412   IN      NS      j.root-servers.net.
.                       26412   IN      NS      a.root-servers.net.
.                       26412   IN      NS      l.root-servers.net.
.                       26412   IN      NS      e.root-servers.net.
.                       26412   IN      NS      g.root-servers.net.
.                       26412   IN      NS      k.root-servers.net.
.                       26412   IN      NS      d.root-servers.net.
.                       26412   IN      NS      h.root-servers.net.
.                       26412   IN      NS      i.root-servers.net.
.                       26412   IN      NS      c.root-servers.net.
.                       26412   IN      NS      m.root-servers.net.
.                       26412   IN      NS      f.root-servers.net.
.                       26412   IN      NS      b.root-servers.net.
;; Received 228 bytes from 4.2.2.1#53(4.2.2.1) in 34 ms

arpa.                   172800  IN      NS      A.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      H.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      C.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      L.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      F.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      M.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      G.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      E.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      D.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      I.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      B.ROOT-SERVERS.NET.
arpa.                   172800  IN      NS      K.ROOT-SERVERS.NET.
;; Received 495 bytes from 192.58.128.30#53(j.root-servers.net) in 28 ms

12.in-addr.arpa.        86400   IN      NS      DMTU.MT.NS.ELS-GMS.ATT.NET.
12.in-addr.arpa.        86400   IN      NS      CMTU.MT.NS.ELS-GMS.ATT.NET.
12.in-addr.arpa.        86400   IN      NS      CBRU.BR.NS.ELS-GMS.ATT.NET.
12.in-addr.arpa.        86400   IN      NS      DBRU.BR.NS.ELS-GMS.ATT.NET.
;; Received 143 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 153
ms

126.95.43.12.in-addr.arpa. 172800 IN    CNAME
126.112-28.95.43.12.in-addr.arpa.
112-28.95.43.12.in-addr.arpa. 172800 IN NS      ns2.nightowl.net.
112-28.95.43.12.in-addr.arpa. 172800 IN NS      mail.nightowl.net.
;; Received 117 bytes from 12.127.16.69#53(CMTU.MT.NS.ELS-GMS.ATT.NET)
in 60 ms

ns2.nightowl.net/mail.nightowl.net is broken (missing
128-28.95.43.12.in-addr.arpa) zone.

For someone who is a CCNA, Mikrotik Certified Whatever, etc, etc, etc,
you really should know how to use dig(1).

William

Current thread:

Tracking down reverse for ip Dennis Burgess (Apr 15)
- Re: Tracking down reverse for ip Larry Sheldon (Apr 15)
- Re: Tracking down reverse for ip Jack Carrozzo (Apr 15)
- RE: Tracking down reverse for ip Joe Johnson (Apr 15)
  - Re: Tracking down reverse for ip Patrick Muldoon (Apr 15)
- Re: Tracking down reverse for ip Jeroen van Aart (Apr 15)
- Re: Tracking down reverse for ip Chris Owen (Apr 15)
  - RE: Tracking down reverse for ip Dennis Burgess (Apr 15)
- Re: Tracking down reverse for ip William Pitcock (Apr 15)
  - Re: Tracking down reverse for ip James Hess (Apr 15)
    - Re: Tracking down reverse for ip Scott Howard (Apr 16)
  - Re: Tracking down reverse for ip Lamar Owen (Apr 16)
- Re: Tracking down reverse for ip Dennis Mbogo (Apr 15)