From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adrian Zaugg <ipfire.org@mailgurgler.com>
To: ddns@lists.ipfire.org
Subject: Re: Passing key algo to nsupdate
Date: Sun, 03 Apr 2022 14:15:24 +0200
Message-ID: <1985172.IPymiuymL7@haiash>
In-Reply-To: <117777420.ruKscuAWOa@haiash>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1550180013639526324=="
List-Id: <ddns.lists.ipfire.org>

--===============1550180013639526324==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi there

After some digging in the code I found some Problems with the ddns component =

of IPFire and especially with the nsupdate provider. The main thing which=20
renders the nsupdate provider unusable, I reported under Bug #12837 [1]. It=20
seems to me there are more problems, but since I don't use IPFire, I do not=20
feel to get involved to much.

It seems to me that the scriptlet the nsupdate provider produces is missing=20
the "update" commands. It connects, authenticates and saves, but does not pas=
s=20
any information to the server. A generated scriptlet for nsupdate should look=
=20
like this:

	server $SERVER
	zone $ZONE
	update delete $HOSTNAME $RR
	update add $HOSTNAME $TTL $RR $IP
	send

...where:=20
$SERVER is the name server to send the record update/ deletion
$ZONE is the domain in which to update the host record
$HOSTNAME is the dynamic host's FQDN
$TTL is the time to live value for the record
$IP is the numerical IP address of the dynamic host
$RR is the record type, "A" for an IPv4, "AAAA" for an IPv6 host address

If I watch the debug output of ddns I do not see the update command being=20
sent. I did not check this good enough to report a bug.

The whole provider does not work at all and the code in the ddns seems half=20
baken to me. I started to report bugs, but I gave up, when I saw, that it=20
nsupdate doesn't work at all. So if some one corrects the code and tests it=20
(who actually knows to code in Python unlike me), those deficiencies should=20
get discovered anyway. I hope I could help with some bug reports against the =

ddns core and the hint in this mail here.

Best regards, Adrian.

[1] https://bugzilla.ipfire.org/show_bug.cgi?id=3D12837

--===============1550180013639526324==
Content-Type: application/pgp-signature
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="signature.asc"
MIME-Version: 1.0

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUFCQ2dBZEZpRUU3NjJueUpiallw
QTJGeUs0WDN3cDBqUlhSbU1GQW1KSmo5d0FDZ2tRWDN3cDBqUlgKUm1OemtSQUFxZDVPMVZvc00x
RGNOTGxkaVZwTTEvQ1Q2Q0IzOC9sTGRWQ0E2SnVRVk5YN1NJN1lleVRzN1dHMApsREJOS3I3Kyto
NW80RWRvYmZHejNjUDE4T1FibmpJbzAzSGZhNGtkUHBrYnFPWkV1NmVhQzZPRmpDajNITHpBCmpu
U1NhSzZtY1d2dWdmcXRLTTBaSFRwYUJLUEl6Znp2UGhIUFZjQ2dFMWtSMWFJVTVJL2Vwd1UzOHN6
VmtHR3MKdXNHZzBVVllESXViL25GUTRvN0lDZmtxNEo1MnF1Ui9QSjRoQVUvTjdYU2Y1MXJpNmNK
b0VmTVlCVmhpQlpHVgp3OElzNkVVeE14bmVMMnQzQVJtK2JYWFBVeFFyc1dzcGdHblkxa2pMWTg1
N253YzQxR0xiaUkrakw5QXBNLzdKClJEZVhzZXRZNjFMU2dnYlFZNDR2Vlo2VHMvUXI3ZTBNVGhn
cVgxT1l3RzErVmd5TWdBdkVKOFlGWnhQY0dML3oKbUdwWDBHRDhjRU9ab2lGTGpuTTlueEE1UWZp
dU9nVnZPRENib2RoSE1JN05FSm9yZ2g2bU5YL3RwbGQ2K0pMcwpIWDRadVVNb1FrSFlyM1RiWWJQ
c09WRGdpbWtCTnpYaUhYSzRob2dUQ2hDZ0lwTkJWZmNOUE9LaTdna2NKQ0JyCk9hczExbWZ3eUor
K2JsbktERkZxS05CT2swWmtNNDdNQjZNZDB3OFNXUkFqOFlDK2xrTXlxazA0UnFBMkRwWEQKZlJ6
ellMbVlaSW1vN2I0UUI4eGZzKzgrRWkrUXFBa05jT0YzUWttNzhla1ZZMjI1cDJiZ0h4WkhkMGs1
TFhYYgpGVHZGWnM0VEY5SG05Ym1TTmxXSTliTlpXRXh2TEV3cnd0U2kvQjZhaE9WRXJzeVBsMlk9
Cj12R01ECi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo=

--===============1550180013639526324==--