README.md

@@ -82,8 +82,3 @@ We can find the zone files  in `/etc/bind/zones`, although note that your zone m
 ```bash
 named-compilezone -f raw -F text -o - blacka.com /etc/bind/zones/blacka.com.signed
 ```
-
-If using the script that runs the version in our container, note that you may have to use the paths that work *inside the container*.  The current script mounts your current working directory, so you can use `run_named_compilezone.sh ./some.zone`, but not `run_named_compilezone.sh /etc/named/zones/blacka.com`.
-
-That said, we are probably better off just using the version that comes with our OS, and not using the container.
-

cfg/named.options.conf

@@ -6,8 +6,8 @@ options {
     lock-file "/var/cache/bind/named.lock";
 
     listen-on { any; };    
-    listen-on-v6 { any; };
+    listen-on-v6 { ::1; };
     allow-recursion { 127.0.0.1; ::1; };
 
-    dnssec-validation yes;
+	dnssec-validation yes;
 };

run_named-compilezone.sh

@@ -1,8 +1,4 @@
 #! /bin/bash
 [ -x "$(which docker 2>/dev/null)" ] && DOCKER=docker
 [ -x "$(which podman 2>/dev/null)" ] && DOCKER=podman
-
+$DOCKER exec bind9 named-compilezone "$@"
-$DOCKER run -ti --rm --name=bind9-tools --network=host \
-    -v "$(pwd):$(pwd)" -w "$(pwd)" \
-    docker.io/internetsystemsconsortium/bind9:9.18 named-compilezone "$@"
-