Syntex for primary/secondary

2020-07-05 Thread @lbutlr
When seeing up a secondary zone what do I replace # with in following (the old syntax was masters instead od master, so I am guessing it needs a new keyword)? zone "example.com" { type secondary; # { 192.168.10.1; }; file "/var/lib/bind/db.example.com"; }; in

Re: unknown option 'trust-anchors'

2020-07-05 Thread Mark Andrews
Yes, that is the issue. > On 6 Jul 2020, at 08:36, @lbutlr wrote: > > On 05 Jul 2020, at 07:51, @lbutlr via bind-users > wrote: >> mail # rndc reload >> rndc: 'reload' failed: failure >> mail # tail /var/log/messages >> Jul 5 07:41:24 mail.covisp.net named[53940] >>

Re: unknown option 'trust-anchors'

2020-07-05 Thread @lbutlr
On 05 Jul 2020, at 07:51, @lbutlr via bind-users wrote: > mail # rndc reload > rndc: 'reload' failed: failure > mail # tail /var/log/messages > Jul 5 07:41:24 mail.covisp.net named[53940] > /usr/local/etc/namedb/bind.keys:29: unknown option 'trust-anchors' > Jul 5 07:41:24 mail.covisp.net

Re: $INCLUDE Kexamle.com.+007...

2020-07-05 Thread @lbutlr
On 05 Jul 2020, at 10:12, Tony Finch wrote: > @lbutlr wrote: > >> When a domain configuration file contains an include line for the key, >> where is that include looking for the key file? > > ... good question, I have avoided having to find that out ... Heh. > So it sounds like "the current

Re: $INCLUDE Kexamle.com.+007...

2020-07-05 Thread Tony Finch
@lbutlr wrote: > When a domain configuration file contains an include line for the key, > where is that include looking for the key file? ... good question, I have avoided having to find that out ... > I'm in a situation where the keys seems to work fine for updating > DNSSEC, but nsdiff

unknown option 'trust-anchors'

2020-07-05 Thread @lbutlr via bind-users
In named.conf I have dnssec-enable yes; dnssec-validation auto; # rndc managed-keys status view: _default next scheduled event: Sun, 05 Jul 2020 20:43:00 GMT name: . keyid: 20326 algorithm: RSASHA256 flags: SEP next refresh: Sun, 05 Jul 2020