SUMMARY: Reverse Mapping for Dynamically Asigned IP Adresses

From: SSGSD OL-B/SDTO (devon@ssgsd-www.tinkernet.af.mil)
Date: Wed Sep 18 1996 - 10:34:52 CDT


Thanks to everyone who took time to contact me and try to steer me in the right
direction:

        Jim Craven (craven@cg.NRCan.gc.ca) - suggested that O'Reilly's DNS book
                                             mentions that reverse mapping will
                                             be dropped.

         Frank Pardo (fpardo@mail.tisny.com) - recommended IPng and the TCP/IP
                                              Protocols by Stephen A. Thomas

         Rob Vahsen (vahsenr@ce.philips.nl) - recommended O'Reilly's DNS & Bind
                                              book and Sunsolve CD's

I didn't see anything in O'Reilly's DNS & Bind book, and don't have IPng and the
TCP/IP Protocols (but I'll look for it when I get a chance).

The solution we'll try to implement came from a local UNIX "guru" who
recommendid mapping to an address oriented scheme rather than a name:
(Thanks to Brent Haught, a dear friend and brother in the Lord, who
always seems to have the right answer):

1) Create a bogus "hostname" based on the last two octets of the IP address.
For example, the IP 131.18.20 subnet would look like this (with MX records
pointing to the actual user's MS Mail server (in my case)):

        $ORIGIN TINKERNET.AF.MIL.

        PC20-1 IN A 131.18.20.1
                        IN MX 0 COMSWSYS.TINKERNET.AF.MIL.
        PC20-2 IN A 131.18.20.2
                        IN MX 0 COMSWSYS.TINKERNET.AF.MIL.
        .
        .
        .
        PC20-254 IN A 131.18.20.254
                        IN MX 0 COMSWSYS.TINKERNET.AF.MIL.

2) The reverse mapping would work the same way:

        $ORIGIN 20.18.131.IN-ADR.ARPA

        1 IN PTR PC20-1.TINKERNET.AF.MIL.
        2 IN PTR PC20-2.TINKERNET.AF.MIL.
        .
        .
        .
        254 IN PTR PC20-254.TINKERNET.AF.MIL.

Since we're moving to NT servers and WIN95, Brent suggests we can use DHCP
and WINS Administration on the NT Server to isolate the WIN95 or NT
workstation associated with an IP if we need to track down a culprit.

My Original post was:

> Date: Thu, 12 Sep 1996 10:59:39 -0500
> From: Bob Devonshire (SSGSD OL-B/SDTO) <devon@ssgsd-www.tinkernet.af.mil>
> Reply-To: Bob Devonshire (SSGSD OL-B/SDTO) <devon@ssgsd-www.tinkernet.af.mil>
> To: sun-managers@ra.mcs.anl.gov
> Subject: Reverse Mapping for Dynamically Assigned IP Addresses
>
> Would appreciate any guidance available on setting up reverse mapping for
> dynamically assigned IP addresses. We're presently running Solaris 2.3,
> supporting a subnet with some 300 users who have static IP addresses. The
> organization is planninng on moving to NT servers using dynamic IPs. If
> someone has set this up, I'd appreciate any information you have, or pointers
> to FAQ, white paper, books, & etc. Thanks,
>
> -Bob-



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:10 CDT