Path: ames!elroy.jpl.nasa.gov!lll-winken.llnl.gov!uwm.edu!news.alpha.net!news.mathworks.com!mvb.saic.com!vmsnet-sources
Newsgroups: vmsnet.sources
From: Mark.Berryman@Mvb.Saic.Com
Subject: Reverse_Address.Com - automate PTR records in your DNS
Date: Wed, 02 Nov 1994 21:41:32 GMT
Message-ID: <33124354@MVB.SAIC.COM>
Organization: Science Applications Int'l, Corp. - Health-Care Technology Group
Lines: 667
Followup-To: vmsnet.sources.d
Approved: Mark.Berryman@Mvb.Saic.Com

Submitted-by: Mark.Berryman@Mvb.Saic.Com
Posting-number: Volume 7, Issue 29
Archive-name: reverse_address/part01

    For some time now I  have  had  a  procedure, written in MUMPS, which
    fully  automated the process of maintaining the PTR (reverse address)
    records for our corporation within our Domain Name Server.

    I have converted  the  MUMPS  portion  to  DCL  (it's slower but more
    people  have  DCL  than have MUMPS) and herewith submit  the  result.
    There are several assumptions built into this  procedure,  which  are
    documented at the end, but the gist of them is as follows:

        This procedure is  written  for Multinet.  Information needed
        to  convert this procedure to other TCP/IP vendors'  products
        is contained in the assumptions at the end of the procedure.

        This procedure needs to run on  a  system that is acting as a
        primary  or  secondary server for all domains and  subdomains
        comprising the network(s) for  which  this  procedure  is  to
        build  the  reverse-address  zone files.  It is not necessary
        that the system be advertised as  a server, only that it have
        a  local copy of all relevant data (which will always be  the
        case if it is a primary or secondary  server).   This  method
        was  also chosen in order to eliminate the problems caused by
        temporary network outages.

        The necessary  input  files  and  any  restrictions regarding
        their  format are documented in the assumptions at the end of
        the procedure.

        As written, this procedure  runs  as a batch job resubmitting
        itself  for each night at 11:30pm.  However, all of the batch
        commands are contained at the top of  the  procedure  if  you
        wish to modify them.

    I submit this in the hope that someone else may find it useful.  As
    always, comments and suggestions are most welcome.

Mark Berryman
Mark.Berryman@Mvb.Saic.Com