On 08/12/14 08:43, Tom Horsley wrote: > I am trying to adapt all the config from an ancient (fedora 13) > system where the disk died to the new disk I figured I might as > well go ahead and update to centos 7. > > Is there anything magical I need to do to get bind and > bind-chroot working? I've not found any need for "magic". > > It looks sort of like the bind-chroot-setup service will > automagically copy the config files into the chroot. I know nothing about config files being copied. I simply keep all things under /var/named/chroot/ > > What about additional zone files? Do I put them directly > in the chroot directory, or do they get copied too? See above... > > Is there any doc somewhere on the web for bind under > systemd? (A quick google search didn't seem to turn > up anything obvious). I only have named-chroot.service enabled. > > I also seem to remember a recent thread here about > how to make things really wait for the network > to be "up" and services like named not starting properly > all the time. Any conclusions about the best way to > fix that? I run with NetworkManager-wait-online.service enabled. Mostly everything is fine. I've one issue for which there is an outstanding bugzilla. If running named on a system doing nfs mounts they will fail initially on boot if you specify a hostname. I've not spent too much time on it since there is an easy workaround. -- If you can't laugh at yourself, others will gladly oblige. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
