From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Wed, 28 Jan 2015 20:11:29 +0100 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Message-ID: <20150128191129.GP29856@pengutronix.de> References: <001c01d03a43$e6bcb110$b4361330$@csc-online.eu> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <001c01d03a43$e6bcb110$b4361330$@csc-online.eu> Subject: Re: [ptxdist] nsupdate Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de, thomas.walter@csc-online.eu On Tue, Jan 27, 2015 at 04:14:09PM +0100, Thomas Walter wrote: > I am currently working on a kind of dyndns approach and plan to use nsupd= ate > to make the ddns aware of the new IP. However, it seems that nsupdate is > missing in ptxdist. Is this the case or do I miss something in the > configuration to enable it? Probably it's easier to use https to get the update done. Some time ago I implemented a Perl-CGI that takes parameters via GET and does the matching nsupdate for that. If you're interested: The scripts lives at https://cgi.kleine-koenig.org/cgi-bin/nsupdate call it like: https://cgi.kleine-koenig.org/cgi-bin/nsupdate?hostname=3Dtralala.yourdoma= in&ip4=3D1.2.3.4&ip6=3D::1&key=3D42 (but don't do it with valid data because the GET string ends in the server log). The script is available at https://cgi.kleine-koenig.org/cgi-bin/catnsupdate Best regards Uwe -- = Pengutronix e.K. | Uwe Kleine-K=F6nig | Industrial Linux Solutions | http://www.pengutronix.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de