Re: error reading private key file, ddns_update update failed not found

2018-03-31 Thread Tony Finch
rmcgu...@libretechconsulting.com wrote: > > From within the container. Is named chrooting itself inside the container? :-) (Is the networking setup for LXD less of a disaster area than for Docker? https://www.percona.com/blog/2016/08/03/testing-docker-multi-host-network-performance/ https://www.

Re: error reading private key file, ddns_update update failed not found

2018-03-31 Thread rmcgu...@libretechconsulting.com
Hi Kim, Thank you for your email. I'll give this a shot. I did run dns-signzone on both zones again but I didn't remove the signed zones first. Regards, -Ryan Original Message From: Kim Culhan Sent: Friday, March 30, 2018 06:32 PM To: bind-users@lists.isc.org Subject: Re: er

Re: error reading private key file, ddns_update update failed not found

2018-03-31 Thread rmcgu...@libretechconsulting.com
Hi Tony, From within the container. Regards, -Ryan Original Message From: Tony Finch Sent: Saturday, March 31, 2018 06:17 PM To: i...@libretechconsulting.com Subject: Re: error reading private key file, ddns_update update failed not found CC: bind-users@lists.isc.org >Ryan

Re: error reading private key file, ddns_update update failed not found

2018-03-31 Thread Tony Finch
Ryan McGuire wrote: > If it's relevant, bind is running inside an LXD container. Did you run the diagnostic commands inside the container or in a normal host shell? Tony. -- f.anthony.n.finchhttp://dotat.at/ Rockall: East 4 or 5, increasing 6 or 7, perhaps gale 8 later. Slight or moderate,