Re: cant update 'cz'

On Aug 28 2010, clem...@dwf.com wrote: I am getting the message: cz DNSKEY: please check the 'trusted-keys' for 'cz' in named.conf. And in the past this has meant that something needed to be updated. However, when I pull 'anchors.xml' and run anchors2keys anchors.xml

cant update 'cz'

I am getting the message: cz DNSKEY: please check the 'trusted-keys' for 'cz' in named.conf. And in the past this has meant that something needed to be updated. However, when I pull 'anchors.xml' and run anchors2keys anchors.xml trusted.keys there is no entry for 'cz'. What should I be

trusted.keys

Can someone point me to some documentation on what this 'trusted.keys' stuff is all about? -- Reg.Clemens r...@dwf.com ___ bind-users mailing list

Bind error messages (DNSKEY)

I have recently started getting the following pair of error messages from bind: bg DNSKEY: please check the 'trusted-keys' for 'bg' in named.conf.: 6 Time(s) bg DNSKEY: unable to find a DNSKEY which verifies the DNSKEY RRset and also matches one of specified trusted-keys for

9.7.0a2 - deny-answer-addresses

the current usage szenario, if I understood the configuration correctly, is only suited to domain owners running split horizon. But maybe this is a bug? clemens ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo

Re: 9.7.0a2 - deny-answer-addresses

I believe that! I must have read these lines dozens of times but missed the obvious duplication! Not supported in a type forward zone. deny-answer-addresses might be helpful in forwarding and maybe even server zones. clemens ___ bind-users mailing