I reckon I've narrowed it down to the fact that the DNS server is not
accepting the key it's being offered.
The final transaction I receive from an nsupdate exchange offers;
---
;; TSIG PSEUDOSECTION:
domain1_ke
> "Kyle" == Kyle writes:
Kyle> Ah, ok. Thanks for the explanation John.
Kyle> I have never before had to use nsupdate. I just tried it because
Kyle> Peter suggested it and I figured it's a way to test dns updates
Kyle> manually.
Yes --- it'll check that the key you have actually works,
Peter Chubb said:
> as root, do
>lspci -v
>
> It'll tell you which driver module is associated with each PCI device.
Bikeshed issue, but can I suggest:
$ lspci -k
It also shows what kernel module is associated with the device, but
without all the other verbose fluff.
Case in point, this:
Ah, ok.
Thanks for the explanation John.
I have never before had to use nsupdate. I just tried it because Peter
suggested it and I figured it's a way to test dns updates manually.
I have always used BIND with rndc.key and it used to work. What's then
the difference between nsupdate and rndc
