djbdns
[Top] [All Lists]

Re: dynamic dns foo

To: dns@list.cr.yp.to
Subject: Re: dynamic dns foo
From: Sascha Silbe <sascha-ml-cr.yp.to-dns@silbe.org>
Date: Mon, 19 Feb 2007 19:23:53 +0100
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-djbdns@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list dns@list.cr.yp.to
In-reply-to: <20070219133843.GA39128@nilpotent.org>
Mail-followup-to: dns@list.cr.yp.to
Mailing-list: contact dns-help@list.cr.yp.to; run by ezmlm
References: <20070219133843.GA39128@nilpotent.org>
User-agent: Mutt/1.5.11
On Mon, Feb 19, 2007 at 05:38:20AM -0800, Faried Nawaz wrote:

How are people doing dynamic dns (like dyndns.org)?
We're using ssh with keys and forced commands for that. Simple clients just "login" and their source address is used to update the record (this even works behind NAT routers because the address is determined on the server). For more complex setups we're transferring a whole "zone" file (by piping it into ssh) with syntax+security checks (like allowed domain) on the server. Because of tinydns this is quite easy to do. My own server doesn't support DNS updates via HTTP (like dyndns.org et al. do it), but some others do because it's the only thing most NAT routers support (AFAIK not even HTTP_S_). It's basically the same as the simple ssh script, just as CGI.
One thing to remember is to use lock files (setlock from daemontools).

CU Sascha

--
http://sascha.silbe.org/

Attachment: pgpgNjpmb1n8t.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>