From d4dd6bac73bb98d0d064e9b7bdc85d21d04237e8 Mon Sep 17 00:00:00 2001
From: Shahab Dogar <shahab@dogar.dev>
Date: Thu, 24 Oct 2024 13:47:36 +0500
Subject: [PATCH] fix: CoreDNS | configure sequential nameserver usage

This is required for core dns to pick the correct nameservers as
configured by the host's resolv.conf file, according to
https://github.com/k3s-io/k3s/discussions/7822
---
 core-dns/private-dns.yaml | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 core-dns/private-dns.yaml

diff --git a/core-dns/private-dns.yaml b/core-dns/private-dns.yaml
new file mode 100644
index 0000000..407e61e
--- /dev/null
+++ b/core-dns/private-dns.yaml
@@ -0,0 +1,10 @@
+kind: ConfigMap
+apiVersion: v1
+metadata:
+  name: coredns-custom
+  namespace: kube-system
+data:
+  forward.override: |-
+    forward . /etc/resolv.conf {
+      policy sequential
+    }