Ok, thanks John.
I've tried lots since this thread started to the extent I installed a
whole fresh machine on 192 subnet only, skimmed dhcpd and named confs
down to a simple, by the book, 1 domain setup and I still get the same
problem even on the fresh host. And this is a CentOS 5.5 (final)
install. I.e. the latest they publish.
Reply from update query:
;; ->>HEADER<<- opcode: UPDATE, status: _*NOTAUTH*_, id: 39734
;; flags: qr ra ; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 1
;; TSIG PSEUDOSECTION:
domain1.com. 0 ANY TSIG hmac-md5.sig-alg.reg.int.
1297906252 300 16 <someSecretHashHere> 39734 NOERROR 0
If I'm "reserving" an IP for a specific host in dhcpd.conf, am I
supposed to then be already placing a PTR record in the reverse zone
file for the reservation?
If so, doesn't that simply defeat the whole purpose of dhcp?
------------------------------------------------------------------------
Kind Regards
Kyle
On 17/02/11 1:26 PM, John Clarke wrote:
On Tue, Feb 15, 2011 at 07:56:55PM +1100, Kyle wrote:
Sorry for the late reply; I've been busy.
I have always used BIND with rndc.key and it used to work. What's then
the difference between nsupdate and rndc and using BIND?
They have two quite different functions. nsupdate is used to modify
zone data by sending dynamic DNS updates. rndc is used to control the
name server itself, for example, to stop or restart the server, to
reload config and/or zone files.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
