NodeLocal DNS Cache Intercepts all dns queiris about dns

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[aojea]

It is explained here in more detail https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/ , can you explain what are your expectations on what should work differently?

[yahalomimaor]

Sure,
I have to following config in my testing pod,

As you can see the nameserver which is configured is 172.20.0.10 (CoreDNS IP)
and im using ClusterFirst DNS policy which means : "use cluster DNS first, CoreDNS. If the DNS query does not match any domains in cluster DNS, forward it to upstream DNS servers"

So basically im expecting the query to be forward to cordeDNS service.
But when im looking at the logs of the Local-DNS-Cache pod (which runs on the same node with the testing pod)
I can see these quires which sent from the testing pod to the cordeDNS service.

Now the question is:
Why do i see traffic from my testing pod to cordeDNS service, in the Local-DNS-Cache pod?
When the traffic is not even destined to the local-cache.

Does Local-DNS-Cache daemonset, intercept all the dns traffic on the node, even if its destined to cordeDNS service?
if yes, so how it being done?

Thanks,

[aojea]

/transfer kubernetes/dns
/kind support

[k8s-ci-robot]

@aojea: Something went wrong or the destination repo kubernetes/kubernetes/dns does not exist.

In response to this:

/transfer kubernetes/dns
/kind support

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[aojea]

/transfer dns

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale