Re: Bind9 forward/reverse zones with multiple TSIG keys

2019-02-05 Thread ObNox
On 29/01/2019 09:19, ObNox wrote: Following a previous thread (ie: "Selective forwarding?"), I've started to work on a multi-server configuration within 3 sites consisting of a primary at Site1 and secondaries at Site2/3. All sites will have DHCP servers with DDNS enabled. The secondaries will

Re: incorrect section name: $ORIGIN

2019-02-05 Thread @lbutlr
On 4 Feb 2019, at 05:34, Tony Finch wrote: > nsupdate doesn't take zone files as input; OK, then how do I get Bind9.122 to update the .signed files? -- Can't seem to face up to the facts Tense and nervous and I can't relax Can't sleep, bed's on fire Don't touch me I'm a real live wire __

Re: incorrect section name: $ORIGIN

2019-02-05 Thread Tony Finch
@lbutlr wrote: > > OK, then how do I get Bind9.122 to update the .signed files? Did you see my previous message? https://lists.isc.org/pipermail/bind-users/2019-February/101335.html Tony. -- f.anthony.n.finchhttp://dotat.at/ Southeast Iceland: Easterly 7 to severe gale 9, occasionally stor

Re: incorrect section name: $ORIGIN

2019-02-05 Thread @lbutlr
> On 5 Feb 2019, at 04:57, Tony Finch wrote: > > @lbutlr wrote: >> >> OK, then how do I get Bind9.122 to update the .signed files? > > Did you see my previous message? I did not, sorry. > https://lists.isc.org/pipermail/bind-users/2019-February/101335.html >> Are you doing `rndc freeze`

Re: incorrect section name: $ORIGIN

2019-02-05 Thread Tony Finch
@lbutlr wrote: > > No. I was under the impression that when bind reloaded (rndc reload > and/or service named stop/start and/or service named reload) and saw a > new serial number, it would generate a new .signed file for that zone as > part of the process of refreshing its information and notifyi

zone change notification Response: Not implemented

2019-02-05 Thread AL RSM
Hi,   Our master DNS server sends  a "zone change notification" message to serveral slaves for a zone change. All slaves but one responded with no error.  The faulty slave responded with: "Reply code: Not implemented (4)" Slave servers are listining on port 53 for DNS notify.   =