[1836] in linux-net channel archive
Re: dynamic ip's
daemon@ATHENA.MIT.EDU (Daniel B. Harter)
Sun Feb 4 17:34:35 1996
Date: Sun, 4 Feb 1996 15:19:46 -0500 (EST)
From: "Daniel B. Harter" <harterd@citi.net>
To: Chris Woods <cjwoods@paladin.com>
cc: ecarp@netcom.com, linux-net@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.91.960201221155.8666E-100000@bifrost.paladin.com>
On Thu, 1 Feb 1996, Chris Woods wrote:
> On Thu, 1 Feb 1996, Ed Carp, KHIJOL SysAdmin wrote:
>
> > > A name is bound to an IP address. If your IP address changes, your name
> > > changes.
> >
> > Not necessarily. Just tell NIC that your IP address has changed.
>
> If you're referring to the InterNIC, this has nothing at all to do with
> the NIC. The NIC doesn't maintain DNS records for each IP address in use;
> just "pointers" to nameservers that are authoritative for the zone in
> question. To maintain a DNS name while changing your IP address, the DNS
> info for that IP address would have to change. This is, for obvious
> reasons, very inefficient and not feasible in most situations.
That's true. It is conceivable that you could have a dynamic be the
primary DNS for a domain. You would need at least 2 hosts on the
Internet acting as the authoritative servers for the domain.
When the remote server logs in, the local server could reconfigure the
/etc/named.boot depending on the new IP address of the user, then restart
named. The second local server would secondary the first. That would be
enough for Internic, anyway, so the whois table would not constantly be
updated. (It would be easier to assign a static IP, though. :-)
> Chris Woods Systems Administrator
> cjwoods@paladin.com Paladin Computing Solutions
> 617-273-4226 http://www.paladin.com
> "Never underestimate the destructive power of a backhoe." -Brent Chapman
Daniel Harter, Systems/Software Engineer [email] harterd@citi.net
Computer Information Technology, Inc. [phone] (703) 204-4520
2136-C Gallows Rd., Dunn Loring, VA 22027, USA [fax] (703) 204-4530
