'succesful' nsupdate of remote server not persistent across nameserver restart?

jasonsu at mail-central.com jasonsu at mail-central.com
Sun Apr 24 23:39:16 UTC 2016


> This zone would not pass named-checkzone, which interestingly, is the same code which named itself uses when initially loading a zone.

It appears to

	named-checkzone -t /var/chroot/named example.com /namedb/master/example.com.zone
		zone example.com/IN: loaded serial 1461540029
		OK


cat /tmp/nsupdate.txt
	server ns01.example.com
	debug yes
	zone example.com.
	update add test.example.com. 300 in TXT "TEST STRING"
	show
	send

$NSUPDATE /tmp/nsupdate.txt

@ server

	Apr 24 16:24:02 ns01 named[14954]: 24-Apr-2016 16:24:02.350 update-security: info: client 10.0.0.17#26427/key jason-key: view external: signer "jason-key" approved
	Apr 24 16:24:02 ns01 named[14954]: 24-Apr-2016 16:24:02.350 update: info: client 10.0.0.17#26427/key jason-key: view external: updating zone 'example.com/IN': adding an RR at 'test.example.com' TXT "TEST STRING"

TBH I don't understand WHAT to 'expect' from dig to test/verify this^.  What do I dig to get an answer with "TEST STRING" in it?

Jason


More information about the bind-users mailing list