Talk:BIND, dynamic DNS - Revision history

92.226.182.177: /* FQDN error? */ new section

2013-05-11T19:39:10Z

FQDN error?: new section

Jimbo: Reverted edits by 79.142.79.12 (Talk) to last revision by Jimbo

2011-04-01T20:51:43Z

Reverted edits by 79.142.79.12 (Talk) to last revision by Jimbo

79.142.79.12: /* car country language quote residence 175 */ new section

2011-04-01T19:27:04Z

car country language quote residence 175: new section

Jimbo: a little bit of both

2008-08-20T13:28:22Z

a little bit of both

82.182.172.103: (added ~~~~~)

2008-08-20T10:54:05Z

(added ~~~~~)

82.182.172.103: oh

2008-08-20T10:53:22Z

Jimbo at 03:00, 20 August 2008

2008-08-20T03:00:52Z

Jimbo: nope. see '''man nsupdate'''

2008-08-20T02:59:00Z

nope. see '''man nsupdate'''

82.182.172.103: len

2008-08-19T22:41:30Z

len

New page

in set-ddns.pl:

$KEYFILE should probably point to the key file, not the private file.

'''$KEYFILE = 'Kclient.server.net.+157+15661.private';'''
should read
'''$KEYFILE = 'Kclient.server.net.+157+15661.key';'''

par non, complimenteré?

← Older revision		Revision as of 19:39, 11 May 2013
Line 48:		Line 48:

	--[[User:Jimbo\|Jimbo]] 09:28, 20 August 2008 (EDT)		--[[User:Jimbo\|Jimbo]] 09:28, 20 August 2008 (EDT)
		+
		+	== FQDN error? ==
		+
		+	Shouldnt the SOA record in the example zone file be
		+
		+	$ORIGIN .
		+	$TTL 10 ; 10 seconds
		+	client.server.net. IN SOA ......
		+	...
		+	...
		+	$ORIGIN client.server.net
		+
		+	instead of
		+
		+	$ORIGIN .
		+	$TTL 10 ; 10 seconds
		+	client.server.net IN SOA ......
		+	...
		+	...
		+	$ORIGIN client.server.net
		+
		+	? (Note the trailing dot in the SOA line.)

← Older revision		Revision as of 20:51, 1 April 2011
Line 48:		Line 48:

	--[[User:Jimbo\|Jimbo]] 09:28, 20 August 2008 (EDT)		--[[User:Jimbo\|Jimbo]] 09:28, 20 August 2008 (EDT)
−
−	~~== car country language quote residence~~
−	~~175 ==~~
−
−	~~364864~~

← Older revision		Revision as of 19:27, 1 April 2011
Line 48:		Line 48:

	--[[User:Jimbo\|Jimbo]] 09:28, 20 August 2008 (EDT)		--[[User:Jimbo\|Jimbo]] 09:28, 20 August 2008 (EDT)
		+
		+	== car country language quote residence
		+	175 ==
		+
		+	364864

← Older revision		Revision as of 13:28, 20 August 2008
Line 40:		Line 40:

	[[User:82.182.172.103\|82.182.172.103]] 06:54, 20 August 2008 (EDT)		[[User:82.182.172.103\|82.182.172.103]] 06:54, 20 August 2008 (EDT)
		+
		+	== a little bit of both ==
		+
		+	The secret (ha) is that the keyfile HAS to be in the very stilted form mentioned, with both the .private and the .key present in that directory. I discovered the hard way that if you veer from that formula one tiny millimeter, nsupdate breaks with no or extremely unhelpful messages. You also HAVE to be IN the directory in question when you issue the command - specifying the full path to the keyfile isn't enough, you MUST be actually IN that directory.
		+
		+	I suspect the codebase for nsupdate could use some lovin'.
		+
		+	--[[User:Jimbo\|Jimbo]] 09:28, 20 August 2008 (EDT)

← Older revision		Revision as of 10:54, 20 August 2008
Line 38:		Line 38:

	weird or just convenient?		weird or just convenient?
		+
		+	[[User:82.182.172.103\|82.182.172.103]] 06:54, 20 August 2008 (EDT)

← Older revision		Revision as of 10:53, 20 August 2008
Line 30:		Line 30:

	--[[User:Jimbo\|Jimbo]] 22:59, 19 August 2008 (EDT)		--[[User:Jimbo\|Jimbo]] 22:59, 19 August 2008 (EDT)
		+
		+	== oh ==
		+
		+	yes, there I have it (smiley).
		+
		+	however it seems that it does not matter which of the two files I feed to nsupdate -- it works in either case. indeed, ''nsupdate -k Kclient.server.net.+157+15661'' (without the last part, notice) is valid too. well, at least this is true on the debian system I am testing this on.
		+
		+	weird or just convenient?

@@ Line 1: / Line 1: @@
 in set-ddns.pl:
@@ Line 8: / Line 9: @@
 par non, complimenteré?
 == nope.  see '''man nsupdate''' ==

← Older revision		Revision as of 02:59, 20 August 2008
Line 8:		Line 8:

	par non, complimenteré?		par non, complimenteré?
		+
		+	== nope. see '''man nsupdate''' ==
		+
		+	nsupdate uses the -y or -k option (with an HMAC-MD5 key) to provide the
		+	shared secret needed to generate a TSIG record for authenticating
		+	Dynamic DNS update requests. These options are mutually exclusive. With
		+	the -k option, nsupdate reads the shared secret from the file keyfile,
		+	whose name is of the form '''K{name}.+157.+{random}.private'''.
		+
		+	Kinda confusing, I know, but I'm not the one who made the confusion. (Note how the manpage itself refers to the file as "keyfile" in the argument examples; I'm just following the existing conventions by naming my own variable $KEYFILE.)
		+
		+	Reading on in the manpage:
		+
		+	For historical reasons, the file K{name}.+157.+{random}.key must also be
		+	present.
		+
		+	So, there ya have it. =)
		+
		+	--[[User:Jimbo\|Jimbo]] 22:59, 19 August 2008 (EDT)