From 0cb935b5aa31f9a5359e4fae4564e91a6207b346 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Thu, 24 Jun 2021 21:57:48 +0200 Subject: [PATCH] using bind? --- .../kubernetes-dns-entries-nat64/contents.lr | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/content/u/blog/kubernetes-dns-entries-nat64/contents.lr b/content/u/blog/kubernetes-dns-entries-nat64/contents.lr index 800bca3..3fd6a81 100644 --- a/content/u/blog/kubernetes-dns-entries-nat64/contents.lr +++ b/content/u/blog/kubernetes-dns-entries-nat64/contents.lr @@ -119,6 +119,22 @@ abc.something.example.org A In theory this might be solved via some scripting, maybe via a DNS server like powerDNS? +## Alternative solution with BIND + +The bind DNS server, which is not usually deployed in a kubernetes +cluster, supports **views**. Views enable different replies to the +same query depending on the source IP address. Thus in theory +something like that could be done, assuming a secondary zone +*example.org*: + +* If the request comes from the kubernetes cluster, return a CNAME + back to example.com. +* If the request comes from outside the kubernetes cluster, return an + A entry with the static IP +* Unsolved: how to match on the AAAA entries (because we don't CNAME + with the added A entry) + + ## Other solution? As you can see, mixing the dynamic IP generation and coupling it with