Oh, please do not forget to generate new my-tsig after sharing your
current with all of us.
Next time please use named-checkconf -px named.conf.tsigkeys to filter
out secrets.
As Anand already wrote, shared keys are not asymmetric keys generated by
dnssec-keygen. That have been split since 9
On 11/01/2024 12:58, trgapp16 via bind-users wrote:
Hi Mounika,
[snip]
-->With help of the private key i generated one file with name
"named.conf.tsigkeys" at
/etc/bind -
root@dhcpt:/etc/bind# cat named.conf.tsigkeys
key "my-tsig" {
algorithm "ECDSAP256SHA256";
secret "ESkrVALONh
Hello,
Bind version - 9.18.12
-->This is the command I used for generating dnssec-keygen keys -
root@dhcpt: /etc/bind# dnssec-keygen -a ECDSAP256SHA256 -n ZONE example.com
Kexample.com.+013+43215.key
Kexample.com.+013+43215.private
root@dhcpt:/etc/bind# cat Kexample.com.+013+43215.private
Privat
Firstly show what you are actually doing. It it too much for you to actually
cut-and-paste what you are doing?
Secondly BIND 9.18 is at 9.18.22. Version 9.18.8 is seriously out of date.
> On 11 Jan 2024, at 15:21, pvs via bind-users wrote:
>
> Hello,
>
> I'm using ubuntu 22.04 server on
Hello,
I'm using ubuntu 22.04 server on which bind 9.18.8 service is running.
I'm trying to generate dnssec-key by using the command "dnssec-keygen
-a RSASHA512 -b 2048 -n zone example.com"
After doing this, it is generating both public key and private key.
When I generate a file with apr
5 matches
Mail list logo
