Re: DynDNS
On Tue, 17 Mar 1998, Amos Shapira wrote:
> aqy6633@acf5.nyu.edu (Alex Yukhimets) wrote:
> |I don't have any sources, but I also don't think it is a big deal to write
> |one from scratch. We should only agree on communication method. The server
>
> I don't quite get it - whatever DynDNS does, your suggestions seems to
> be allready covered by the current release of Bind 8, from
> /usr/doc/bind/README:
>
> BIND 8 Features
>
> -> DNS Dynamic Updates (RFC 2136)
>
> -> DNS Change Notification (RFC 1996)
> Am I missing something in thinking that RFC 2136 allready defines
> this?
Yes. The 'DynDNS' Tim is looking for is the modification (and then
distribution) of the zone file based on dynamic IP address assignment to
the owner of the domain [ie ppp]. Monolith does this with a HTTP server
running a CGI form that has an account name, password and new IP. the
DynDNS client then simply pulls the IP from the interface and sends a HTTP
POST request to the server, it updates the zone file and then hups bind
(8) which invokes RFC 2136/1996 to update every secondary and presto, you
have a static hostname for a dynamic IP.
Jason
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to:
- Follow-Ups:
- Re: DynDNS
- From: sailer@sun10.sep.bnl.gov (Tim Sailer)
- References:
- Re: DynDNS
- From: Amos Shapira <amos@gezernet.co.il>