Open kiranmaiem opened 2 years ago
Hello @kiranmaiem! Is this what you are looking for https://learn.microsoft.com/en-us/azure/aks/coredns-custom#custom-forward-server?
@andbaraks Documentation points out how to append additionnal configuration with the coredns-custom config map. What @kiranmaiem is trying to do in my understanding is to override the current configuration of Corefile in coredns config map.
I m also looking for a way to add a policy to the forward plugin for ".:53" as were encountering a lot of problems with alpine based images regarding dns resolution.
I am looking for the same functionality. The default configuration helpfully directs requests to resolv.conf but I'd like to be able to specify policy
as sequential instead of the default option of random.
Action required from @Azure/aks-pm
Related issue #2623 in which commenters were asking for similar kinds of functionality.
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
The related ticket (#2623 ) was closed with an answer to use "cluster.local." , but it's insufficient for our setup where we require even external dns names to show up in coredns and have configured PowerDNS to properly provide those. Therefor that answer is insufficient and we need a way to set the forward param for "." (all domains).
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Is there any progress with this request?
Issue needing attention of @Azure/aks-leads
Still interested. Please keep this issue open.
For a hacky workaround see: https://github.com/Azure/AKS/issues/3661#issuecomment-1931883620
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Describe scenario Our business use case mandates that for a given AKS cluster, we need to configure coredns forwarder to a custom DNS server.
Question As i read in the documentation, AKS coredns configuration can't be overridden even with custom config map for core-dns. Is there any other way than changing it on the vNet. We can't take vNet approach as the vNet is shared by various services.