Victor Duchovni a écrit : > On Mon, Jan 12, 2009 at 06:13:52PM -0500, Wietse Venema wrote: > >> David Cottle: >>> Content-Description: Undelivered Message >>> Content-Type: message/rfc822 >>> Content-Transfer-Encoding: 8bit >>> >>> Received: from server.engineering.idb (unknown [127.0.0.1]) >>> by server.engineering.idb (Postfix) with ESMTP id C3F5B13C002D >>> for <webmas...@aus-city.com>; Sun, 11 Jan 2009 23:43:36 +0000 (UTC) >>> Received-SPF: none (no valid SPF record) >>> Received: from hosting.mgapi.edu (unknown [82.179.217.2]) >>> by server.engineering.idb (Postfix) with SMTP >>> for <webmas...@aus-city.com>; Sun, 11 Jan 2009 23:43:35 +0000 (UTC) >>> Received: from dpkpyv (181.138.153.218) >>> by hosting.mgapi.edu; Mon, 12 Jan 2009 02:43:44 +0300 > > Interestingly, the 181.0.0.0/8 Network is IANA reserved: > > OrgName: Internet Assigned Numbers Authority > OrgID: IANA > Address: 4676 Admiralty Way, Suite 330 > City: Marina del Rey > StateProv: CA > PostalCode: 90292-6695 > Country: US > > NetRange: 181.0.0.0 - 181.255.255.255 > CIDR: 181.0.0.0/8 > NetName: NET181 > NetHandle: NET-181-0-0-0-0 > Parent: > NetType: IANA Reserved > Comment: > RegDate: 1993-05-01 > Updated: 2003-04-06 > > I wonder how hosting.mgapi.edu managed to receive connections from the > 181.138.153.218 address. >
maybe MGAPI are using these internally... We've already seen people using the IPs found in "DNS and BIND" (I think these were HP ranges, right?), so confusing "IANA reserved" with "reserved for eternity" (thus "safe for private use") is less surprising ;-p
