Home page logo
/

nanog logo nanog mailing list archives

Re: in-addr.arpa?
From: Valdis.Kletnieks () vt edu
Date: Thu, 15 Jun 2000 02:40:39 -0400


On Thu, 15 Jun 2000 08:04:34 +0200, Hank Nussbacher <hank () att net il>  said:

Why would 216.136.44.104 do something like this?
  14 ip104.44.136.216.in-addr.arpa (216.136.44.104) [AS 4323] 404 msec 400 
;; QUERY SECTION:
;;      104.44.136.216.in-addr.arpa, type = ANY, class = IN
;; ANSWER SECTION:
104.44.136.216.in-addr.arpa.  1D IN PTR  ip104.44.136.216.in-addr.arpa.

;; QUERY SECTION:
;;      44.136.216.in-addr.arpa, type = SOA, class = IN
;; ANSWER SECTION:
44.136.216.in-addr.arpa.  1D IN SOA  ns1.inc.net. hostmaster.inc.net. (

Umm.. because hostmaster () inc net was feeling lazy? ;)

It isn't the first time I've seen people do this.  However,
usually they manage to have the PTR point at something that itself
has an A record that matches.  Alas, there isn't an entry:

ip104.44.136.216.in-addr.arpa. IN A 216.136.44.104

I suppose given the sorry state of the REST of the PTR map, we should
be glad that at least they acknowledged that they own the IP, and
that it didn't give NXDOMAIN on the PTR ;)

                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech



  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]