Merge pull request #282 from beagles/fix_bind_config_issues

Resolve some bind9 configuration issues

Author: openshift-merge-bot[bot]

templates/designatebackendbind9/config-named/options.conf

@@ -1,6 +1,10 @@
 options {
         allow-new-zones yes;
         directory "/var/named-persistent";
+        dump-file "/var/named-persistent/data/cache_dump.db";
+        statistics-file "/var/named-persistent/data/named_stats.txt";
+        memstatistics-file "/var/named-persistent/data/named_mem_stats.txt";
+        secroots-file "/var/named-persistent/data/named.secroots";
 
         # The default for named is to listen on everything and it's controlled
         # by different settings for different IP versions. If the objective is to
@@ -35,4 +39,5 @@ options {
         recursion no;
         version none;
         allow-query-cache { none; };
+        allow-query { any; };
 };

templates/designatebackendbind9/config/designate-bind9-config.json

@@ -21,6 +21,12 @@
       "recurse": "true",
       "perm": "0775"
     },
+    {
+      "path": "/run/named",
+      "owner": "root:named",
+      "recurse": "true",
+      "perm": "0775"
+    },
     {
       "path": "/var/named-persistent",
       "owner": "root:named",

templates/designatebackendbind9/config/named.conf

@@ -2,4 +2,5 @@ include "/etc/named/rndc.key";
 include "/etc/named/rndc.conf";
 include "/etc/named/options.conf";
 include "/etc/named.rfc1912.zones";
+include "/etc/named.root.key";
 include "/etc/named/logging.conf";