From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from smtprelay03.ispgateway.de ([80.67.31.37])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <thomas.walter@csc-online.eu>) id 1YGiXF-0008Kx-CD
	for ptxdist@pengutronix.de; Thu, 29 Jan 2015 07:25:02 +0100
Received: from [188.98.183.181] (helo=CSCPCTW)
	by smtprelay03.ispgateway.de with esmtpa (Exim 4.84)
	(envelope-from <thomas.walter@csc-online.eu>) id 1YGiXF-0000K8-04
	for ptxdist@pengutronix.de; Thu, 29 Jan 2015 07:25:01 +0100
From: "Thomas Walter" <thomas.walter@csc-online.eu>
References: <001c01d03a43$e6bcb110$b4361330$@csc-online.eu>
	<20150128191129.GP29856@pengutronix.de>
In-Reply-To: <20150128191129.GP29856@pengutronix.de>
Date: Thu, 29 Jan 2015 07:24:59 +0100
Message-ID: <001201d03b8c$4ecafb10$ec60f130$@csc-online.eu>
MIME-Version: 1.0
Content-Language: de
Subject: Re: [ptxdist] nsupdate
Reply-To: ptxdist@pengutronix.de, thomas.walter@csc-online.eu
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=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

Good Morning!

Thanks, Uwe, for the Info! It sounds feasible and interesting do it this
way.
I will definitely look into this how it can make things easier.

Regards,
Tom


-----Original Message-----
From: ptxdist-bounces@pengutronix.de [mailto:ptxdist-bounces@pengutronix.de]
On Behalf Of Uwe Kleine-K=F6nig
Sent: Mittwoch, 28. Januar 2015 20:11
To: ptxdist@pengutronix.de; thomas.walter@csc-online.eu
Subject: Re: [ptxdist] nsupdate

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 =

> nsupdate 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.yourdomai=
n&i
p4=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


-- =

ptxdist mailing list
ptxdist@pengutronix.de