<p>Our KOPS based Kubernetes cluster in AWS stopped creating external dns records in Route53 like: service-name-svc.testing.companydomain.com. Is there any way to check what flag is set for the dns-controller working within the cluster? Any other suggestions on how to troubleshoot it are welcomed!</p>
<p>With this in mind, the records like: service-name-svc.namespace.svc.cluster.local resolves fine.</p>
<pre><code>Server:    100.32.0.10
Address 1: 100.32.0.10 kube-dns.kube-system.svc.cluster.local

Name:      service-name-svc.namespace.svc.cluster.local

Address 1: 100.32.12.141 service-name-svc.namespace.svc.cluster.local
</code></pre>

Viji
<p>The typical way of creating route53 records in a kOps cluster is to deploy <a href="https://github.com/kubernetes-sigs/external-dns" rel="nofollow noreferrer">external-dns</a> to the control plane nodes.</p>
<p>dns-controller may create route53 records too, and it does so for kube-apiserver and other system components. However, to use this for other nodes/services, you need to add specific annotations. See the <a href="https://github.com/kubernetes/kops/blob/master/dns-controller/README.md" rel="nofollow noreferrer">dns-controller documentation.</a></p>
