diff --git a/content/u/blog/how-to-configure-bind-dns-for-a-forward-zone-only/background.png b/content/u/blog/how-to-configure-bind-dns-for-a-forward-zone-only/background.png
new file mode 100644
index 0000000..b3b0aff
Binary files /dev/null and b/content/u/blog/how-to-configure-bind-dns-for-a-forward-zone-only/background.png differ
diff --git a/content/u/blog/how-to-configure-bind-dns-for-a-forward-zone-only/contents.lr b/content/u/blog/how-to-configure-bind-dns-for-a-forward-zone-only/contents.lr
index c80b030..bbe2ea5 100644
--- a/content/u/blog/how-to-configure-bind-dns-for-a-forward-zone-only/contents.lr
+++ b/content/u/blog/how-to-configure-bind-dns-for-a-forward-zone-only/contents.lr
@@ -91,7 +91,7 @@ clients, **you can create multiple DNS views**.
 In our case, we have a lot of IPv6 only kubernetes clusters, which are
 named `xx.k8s.ooo` and have a world wide rachable CoreDNS server built
 in. In this case, we want to allow the domain c1.k8s.ooo to be world
-reachable, so we configure the dual stack server
+reachable, so we configure the dual stack server as follows:
 
 ```
 zone "c1.k8s.ooo"  {
@@ -100,3 +100,19 @@ zone "c1.k8s.ooo"  {
    forwarders { 2a0a:e5c0:2:f::a; };
 };
 ```
+
+### Step 4: adjusting the zone file
+
+In case you are running an IPv6 only server, you need to configure the
+upstream DNS server. In our case this looks as follows:
+
+```
+; The domain: c1.k8s.ooo
+c1                          NS      kube-dns.kube-system.svc.c1
+
+; The IPv6 only DNS server
+kube-dns.kube-system.svc.c1 AAAA    2a0a:e5c0:2:f::a
+
+; The forwarding IPv4 server
+kube-dns.kube-system.svc.c1 A       194.5.220.43
+```