Azure CLI container image: possible source of massive DNS TXT queries without running az commands?

### Describe the bug

We deployed the Azure CLI container image in a customer-owned Kubernetes/IDC environment as a CLI runtime environment. At the incident time, the customer confirmed no Azure CLI command was actively executed.

However, the Kubernetes node generated a large number of DNS TXT queries to www.google.com. The node only had APIM Self-hosted gateway and Azure CLI image deployed, so the customer wants to confirm whether the Azure CLI image could trigger such DNS queries by itself.

**DNS Logs:**

_named[1454649]: info queries: client @0x7ff472c66168 10.1**.2**.1**#4960 ([www.google.com](http://www.google.com/)): query: [www.google.com](https://www.google.com/) IN TXT +E(0) (1**.4*.8*.2**)_

### Related command

N/A. No az command was executed when the DNS queries occurred.

### Errors

No Azure CLI error message. DNS server log sample:

named[1454649]: info queries: client @0x7ff472c66168 10.1**.2**.1**#4960 ([www.google.com](http://www.google.com/)): query: [www.google.com](https://www.google.com/) IN TXT +E(0) (1**.4*.8*.2**)

### Issue script & Debug output

N/A. The issue happened without running an az command, so no --debug output is available.

### Expected behavior

If no az command is executed, the Azure CLI container image should not proactively generate massive DNS TXT queries to www.google.com.

### Environment Summary

NA

### Additional context

The issue occurred on Aug 9. The pod was deleted to mitigate the issue, and after recreation the issue cannot currently be reproduced.

We would like to confirm whether Azure CLI image has any built-in background process, telemetry, health check, SDK dependency, or startup behavior that could generate DNS TXT queries without an explicit az command being run.