Why would 216.136.44.104 do something like this? 10 sl-inetconn-1-0-0-T3.sprintlink.net (144.228.207.46) [AS 1239] 200 msec 204 msec 208 msec 11 pa1-atm0-6-bbr01.alby.twtelecom.net (207.250.101.2) [AS 4323] 244 msec 264 m sec 248 msec 12 pa1-atm0-5-acr01.alby.twtelecom.net (216.136.44.242) [AS 4323] 256 msec 252 msec 252 msec 13 learnl-ppp-1130-09-u242.alby.twtelecom.net (207.250.24.30) [AS 3857] 256 mse c 260 msec 256 msec 14 ip104.44.136.216.in-addr.arpa (216.136.44.104) [AS 4323] 404 msec 400 msec 3 80 msec -Hank
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
Um, because someone has a recond in their in-addr.arpa zone file for that IP address that looks like one of the following: 104 IN PTR ip104.44.136.216 or 104 IN PTR ip104.44.136.216.in-addr.arpa. A common mistake is forgetting the "." after the record. This will cause the reverse to show as "what you wanted" + ".in-addr.arpa". --- John Fraizer EnterZone, Inc On Thu, 15 Jun 2000, Hank Nussbacher wrote:
Why would 216.136.44.104 do something like this?
10 sl-inetconn-1-0-0-T3.sprintlink.net (144.228.207.46) [AS 1239] 200 msec 204 msec 208 msec 11 pa1-atm0-6-bbr01.alby.twtelecom.net (207.250.101.2) [AS 4323] 244 msec 264 m sec 248 msec 12 pa1-atm0-5-acr01.alby.twtelecom.net (216.136.44.242) [AS 4323] 256 msec 252 msec 252 msec 13 learnl-ppp-1130-09-u242.alby.twtelecom.net (207.250.24.30) [AS 3857] 256 mse c 260 msec 256 msec 14 ip104.44.136.216.in-addr.arpa (216.136.44.104) [AS 4323] 404 msec 400 msec 3 80 msec
-Hank
Um, because someone has a recond in their in-addr.arpa zone file for that IP address that looks like one of the following:
104 IN PTR ip104.44.136.216
Actually, as the zone is 44.136.216.in-addr.arpa., I'd be tempted to say they've just put 104 IN PTR ip104 Simon -- Simon Lockhart | Tel: +44 (0)1737 839676 Internet Engineering Manager | Fax: +44 (0)1737 839516 BBC Internet Services | Email: Simon.Lockhart@bbc.co.uk Kingswood Warren,Tadworth,Surrey,UK | URL: http://support.bbc.co.uk/
My best guess is someone forgot to put a "." on the end of that reverse DNS entry. On Thu, 15 Jun 2000, Hank Nussbacher wrote:
Why would 216.136.44.104 do something like this?
10 sl-inetconn-1-0-0-T3.sprintlink.net (144.228.207.46) [AS 1239] 200 msec 204 msec 208 msec 11 pa1-atm0-6-bbr01.alby.twtelecom.net (207.250.101.2) [AS 4323] 244 msec 264 m sec 248 msec 12 pa1-atm0-5-acr01.alby.twtelecom.net (216.136.44.242) [AS 4323] 256 msec 252 msec 252 msec 13 learnl-ppp-1130-09-u242.alby.twtelecom.net (207.250.24.30) [AS 3857] 256 mse c 260 msec 256 msec 14 ip104.44.136.216.in-addr.arpa (216.136.44.104) [AS 4323] 404 msec 400 msec 3 80 msec
-Hank
participants (5)
-
Hank Nussbacher -
John Fraizer -
Rodney L Caston -
Simon Lockhart -
Valdis.Kletnieks＠vt.edu