Please remember to reply to the mailing list, not the original sender:
http://gnudip2.sourceforge.net/#mailinglist
+++++++++
See bottom.
> > i got an error message when i doing nsupdate for test, may i know what i'm
> > doing wrong?
> >
> > nsupdate -v -k /usr/local/gnudip/etc/Kgnudip-key.+157+06663.private
> > > update add abc.test.com. 0 A 192.168.1.1
> > >
> > dns_request_getresponse: tsig indicates error
> >
> >
> > my /etc/named.conf
> >
> >
> > include "/etc/gnudip-keyfile";
> >
> > zone "test.com" {
> > type master;
> > file "test.com";
> > allow-query { any; };
> > update-policy { grant gnudip-keyname subdomain test.com; };
> ^^^^^^^^^^^^^^ here you have to use the
> same name as at the key generation (gnudip-key)
> > };
> >
> >
> > my /etc/gnudip-keyfile
> >
> > key gnudip-keyname { here use gnudip-key
> > algorithm hmac-md5;
> > secret "vg4aXFeZTSgdbE2v/n0zQQ==";
> > };
> >
> > my /usr/local/gnudip/etc/Kgnudip-key.+157+06663.private
> ^^^^^^^^^^ this is your keyname: gnudip-key,
> please use this everywhere, and not gnudip-keyname!
> >
> > Private-key-format: v1.2
> > Algorithm: 157 (HMAC_MD5)
> > Key: vg4aXFeZTSgdbE2v/n0zQQ==
>
> I had also this problem. I think there is a little confution in the
> install.html documentation.
>
> Best regards,
> Zoltan
Yes. There was some confusion. I made a change at one point in response
to user feed back, designed to distinguish between the name of the file
included by named.conf, and the name of the key. I stupidly changed
gnudip-key to gnudip-keyname where the key name was used in the
named.conf.
I have fixed this error in both the SourceForge and mini-mirror
versions. The key name is always gnudip-key now.
Thanks.
--
Creighton MacDonnell
http://macdonnell.ca/
--
GnuDIP Mailing List
http://gnudip2.sourceforge.net/#mailinglist
