Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!inetg1!phil
From: phil@inetg1.ARCO.COM (Phil Meyer)
Newsgroups: comp.admin.policy
Subject: Re: IP Number management
Message-ID: <1991May23.150230.29675@Arco.COM>
Date: 23 May 91 15:02:30 GMT
References: <1991May21.203820.11396@ariel.unm.edu>
Sender: phil@inetg1 (Phil Meyer)
Reply-To: phil@Arco.com
Organization: ARCO Oil & Gas Company
Lines: 28

In article <1991May21.203820.11396@ariel.unm.edu>, pkrause@triton.unm.edu (Paul
Krause CIRT) writes:
> Perhaps this is a good group for a discussion of IP number management.  I
> posted to comp.protocols.tcp-ip without much response.  
> 
> We have several thousand numbers out there and while we have a database of
> who is assigned each number, it is static.  With the way people 
> move around, hard drives get trashed, employees are hired or replaced, etc.
> the data gets stale real fast. 
> 
> I gather that dynamic solutions are technically difficult (and probably not
> real intersting to non administrative types).  

Here at ARCO, we are beginning to use DNS to help break up our networks into
smaller more managable sub-domains.  The admin. of each sub-domain is now able
to assign IP address at will, without having to contact the MIS IP address
aministrator.  The use of DNS (domain name service) will automatically update
the tables at the central name server, thus providing a current listing (within
one hour of reality) on demand.

The downsides to DNS are many: SAs must learn DNS, sendmail needs some work,
users don't like using fully qualified host names, etc., etc..

I would also be interested in other peoples solutions.
-- 
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Phil Meyer         phil@arco.com  Work:(214) 754-6805                      |
+=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+