RE: What is up with 170.36.0.0/16

["Vivien M." <vivienm () dyndns org>]

> -----Original Message-----
> From: owner-nanog () merit edu [mailto:owner-nanog () merit edu]On Behalf Of
> Josh Richards
> Sent: June 14, 2001 11:23 AM
> To: nanog () merit edu
> Subject: Re: What is up with 170.36.0.0/16
>
> Just what it says.  They don't appear to be announcing their block. :-)
> (same results here from several boxes I checked, BTW)
>
> Note though that only two of their MX boxes are in that block:
>
> fleet.com       preference = 30, mail exchanger = bkb-bh.bkb.com
> fleet.com       preference = 40, mail exchanger = testmail.fleet.com
> fleet.com       preference = 10, mail exchanger = sweeper.bkb.com
> fleet.com       preference = 20, mail exchanger = walmail.bkb.com
> fleet.com       preference = 10, mail exchanger = mail2.fleet.com
> fleet.com       preference = 20, mail exchanger = bosmail.bkb.com
> fleet.com       preference = 20, mail exchanger = fleet-cp.fleet.com
> fleet.com       nameserver = dnsauth3.sys.gtei.net
> fleet.com       nameserver = dnsauth1.sys.gtei.net
> fleet.com       nameserver = dnsauth2.sys.gtei.net
> bkb-bh.bkb.com  internet address = 204.167.53.66
> testmail.fleet.com      internet address = 170.36.73.48
> sweeper.bkb.com internet address = 155.182.19.38
> walmail.bkb.com internet address = 32.97.32.201
> mail2.fleet.com internet address = 170.36.73.11
> bosmail.bkb.com internet address = 204.167.53.91
> fleet-cp.fleet.com      internet address = 199.95.175.66
> dnsauth3.sys.gtei.net   internet address = 4.2.49.4
> dnsauth1.sys.gtei.net   internet address = 4.2.49.2
> dnsauth2.sys.gtei.net   internet address = 4.2.49.3
>
> Have you tried contacting the technical contact listed in the
> WHOIS record?
> Or perhaps GTEI (Genuity) who appears to be their service provider?

Are you sure this couldn't be intentional?

I've once seen a setup where you had the lowest-priority MX (by that, I mean
the one with the lowest number, in case my wording is ambiguous or
contradictory) being some host with an RFC 1918 IP, and then there was a
higher-priority MX which was their NAT box. I'm guessing (I never sent mail
there, or worked with this setup, thank god) that the idea was that
connections to the RFC 1918 box would die, so remote MTAs would contact the
NAT box and deliver there. The NAT box would then try to relay to the
primary MX, and since it would obviously have an interface into the network
with the RFC 1918 IPs, it would be able to deliver.
This place doesn't seem to be using this setup anymore, although amusingly
enough most of their NS records point to machines with 10.200 IPs.

I agree that this type of thing is entirely dumb, but is there any reason
that the network mentioned by the original poster couldn't be doing the same
thing?
Many large corporations that have been running IP networks since before Wall
Street knew the meaning of the word Internet have different real blocks of
IP space (usually in the class B space) for their "public" network and their
corporate network...

You may also want to take a look at this:
vivienm@citrine:~$ whois -a 170.36.73.11
Fleet Services Corporation (NET-FLEET)
   Mail Stop NY/KP/0104
   Peter D. Kiernan Plaza
   Albany, NY 12207
   US

   Netname: FLEET
   Netblock: 170.36.0.0 - 170.36.255.255
   Maintainer: FSCO

   Coordinator:
      Ryan, Tom  (TR23-ARIN)  postmaster () FLEET COM
      (518) 447-2241

   Record last updated on 02-Feb-2001.
   Database last updated on 13-Jun-2001 23:03:57 EDT.

The ARIN Registration Services Host contains ONLY Internet
Network Information: Networks, ASN's, and related POC's.
Please use the whois server at rs.internic.net for DOMAIN related
Information and whois.nic.mil for NIPRNET Information.

It seems slightly odd to me that this block seems to have no DNS servers
listed for reverse lookups if it is in public use.

Vivien
--
Vivien M.
vivienm () dyndns org
Assistant System Administrator
Dynamic DNS Network Services
http://www.dyndns.org/