"I'm encountering an error when trying to connect to my AKS cluster: dial tcp: lookup nslnew-75778846.hcp.eastus.azmk8s.io on 127.0.0.53:53: no such host.

Question

"I'm encountering an error when trying to connect to my AKS cluster: dial tcp: lookup nslnew-75778846.hcp.eastus.azmk8s.io on 127.0.0.53:53: no such host.

nslaksauto 0

Title: Kubernetes Cluster Connectivity Issue: Unable to Reach API Server

Hi Azure Support Team,

I'm experiencing a connectivity issue with my AKS cluster. When I try to interact with the Kubernetes API, I receive the following error:

dial tcp: lookup nslnew-75778846.hcp.eastus.azmk8s.io on 127.0.0.53:53: no such host

Here are the details of my setup:

Azure service: AKS
Current context set to my cluster: nsl-clusternew
Configuration: I'm using Terraform to manage my resources.

I have tried updating my kubeconfig and ensuring that my network settings are correct, but the issue persists.

Could you please assist me in troubleshooting this connectivity issue?

Thank you!

Lalitha

8555010300

Anusree Nashetty 4,380 Reputation points Microsoft External Staff Moderator

2024-10-18T01:07:03.84+00:00

Hi nslaksauto,

Welcome to the Microsoft Q&A Platform. Thank you for posting your query here. We are looking into it and will get back to you soon.

We recommend not to add any PII information like email/phone number on the open forum for your privacy. You can delete the comments that contains your personal details.

We don't have the ability to connect via phone call or email since it is public forum. However, I would be happy to help you here.

Thank you.
Anusree Nashetty 4,380 Reputation points Microsoft External Staff Moderator

2024-10-21T05:37:31.6133333+00:00

Hi nslaksauto,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, if you have any further queries, please do let us know we will try to help.

Thank you.

1 answer

Your answer

Anusree Nashetty 4,380 Reputation points Microsoft External Staff Moderator

2024-10-18T01:07:03.84+00:00

Hi nslaksauto,

Welcome to the Microsoft Q&A Platform. Thank you for posting your query here. We are looking into it and will get back to you soon.

We recommend not to add any PII information like email/phone number on the open forum for your privacy. You can delete the comments that contains your personal details.

We don't have the ability to connect via phone call or email since it is public forum. However, I would be happy to help you here.

Thank you.
Anusree Nashetty 4,380 Reputation points Microsoft External Staff Moderator

2024-10-21T05:37:31.6133333+00:00

Hi nslaksauto,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, if you have any further queries, please do let us know we will try to help.

Thank you.

Answer 1

Hi nslaksauto,

I have shared troubleshooting steps that I felt will help resolve the issue you reported.

Check that your AKS cluster is running and healthy. You can do this by running the following command, this will tell the provisioning state of your AKS cluster. If the state is Succeeded, then your AKS cluster is running and healthy:

az aks show --resource-group <resource-group-name> --name <aks-cluster-name> --query 'provisioningState'

Check that your DNS settings are correct. This below command will list all the services in your AKS cluster. Make sure that the kube-dns service is running and healthy.

kubectl get svc --all-namespaces

Try updating Kubeconfig: az aks get-credentials --resource-group <resource-group> --name <cluster-name>

If your AKS cluster is public, DNS should resolve directly via Azure's public DNS. If it is private, ensure that you're using private DNS correctly, and that your local network has access to the Azure Private Link endpoints. If it returns true, it means you're using a private cluster, which requires specific VNet and DNS configurations

az aks show --resource-group <resource-group> --name <cluster-name> --query "apiServerAccessProfile.enablePrivateCluster"

If you still find any difficulties, please let me know I would like to work closer on this issue.

Thank you.

Anusree Nashetty 4,380 Reputation points Microsoft External Staff Moderator

2024-10-24T01:04:58.19+00:00

Hi nslaksauto,

I hope you're doing well. Just checking in to see if you had a chance to see my response to your question. If you have any further queries, please do let us know.

If the answer is helpful, please click "Accept Answer" and "Upvote it" as it can be helpful to others in the community.

Share via

"I'm encountering an error when trying to connect to my AKS cluster: dial tcp: lookup nslnew-75778846.hcp.eastus.azmk8s.io on 127.0.0.53:53: no such host.

1 answer

Your answer