Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DNS resolve in azure aks kubernetes cluster seems to behave strange

See original GitHub issue

VERSION M11-SNAPSHOT ISSUE: DNS resolves not correct ENV: Microsoft AKS Kubernetes Cluster

cat /etc/resolv.conf

nameserver 10.0.0.10
search hono.svc.cluster.local svc.cluster.local cluster.local randomname12315135153.ax.internal.cloudapp.net
options ndots:5

BEHAVIOUR: someaddressregisterd.servicebus.windows.net gets resolved/changed to someaddressregisterd.servicebus.windows.net.randomname12315135153.ax.internal.cloudapp.net where randomname12315135153.ax.internal.cloudapp.net is the last search entry in resolv.conf

hono-service-messaging log:

11:59:10.665 [vert.x-eventloop-thread-1] DEBUG o.e.h.c.ConnectionFactoryImpl - connecting to AMQP 1.0 container [amqp://someaddressregisterd.servicebus.windows.net:5671]
11:59:11.176 [vert.x-eventloop-thread-1] DEBUG o.e.h.c.ConnectionFactoryImpl - can't connect to AMQP 1.0 container [amqp://someaddressregisterd.servicebus.windows.net:5671]: Search domain query failed. Original hostname: 'someaddressregisterd.servicebus.windows.net' failed to resolve 'someaddressregisterd.servicebus.windows.net.5ktyvdc02vkuti5b2n4gshahuf.ax.internal.cloudapp.net' after 3 queries
11:59:11.177 [vert.x-eventloop-thread-1] INFO  o.e.h.t.i.ForwardingTelemetryDownstreamAdapter - failed to connect to downstream container: Search domain query failed. Original hostname: 'someaddressregisterd.servicebus.windows.net' failed to resolve 'someaddressregisterd.servicebus.windows.net.5ktyvdc02vkuti5b2n4gshahuf.ax.internal.cloudapp.net' after 3 queries

nslookup someaddressregisterd.servicebus.windows.net works (ip and hostname resolves) ping someaddressregisterd.servicebus.windows.net works (ip resolves) telnet someaddressregisterd.servicebus.windows.net 5671 works custom qpid client deployed to the same cluster connecting same address works

EXPECTED someaddressregisterd.servicebus.windows.net can be resolved correctly

Issue Analytics

State:
Created 6 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

sophokles73commented, Feb 16, 2018

see #331

0reactions

sophokles73commented, Mar 12, 2018

@bsukramlitt can we close this issue?

Top Results From Across the Web

DNS resolve in azure aks kubernetes cluster seems to behave ...

I can now confirm that the issue is not related to k8s at all. Yes there was a DNS issue but the ExternalName...

Azure - Troubleshoot - Microsoft Learn

When you try to create an AKS cluster, you receive the following error message: Agents are unable to resolve Kubernetes API server name....

DNS doesn't remove not ready pod in AKS with Azure CNI ...

Any pods created by a Deployment or DaemonSet exposed by a Service have the following DNS resolution available: pod-ip-address.deployment-name.

Troubleshooting Kubernetes Services Part 2 - Sysdig

Check out this post on troubleshooting Kubernetes services. A Sysdig and Kubernetes adventure. Download the complete guide today.

RQs answer (3) - Zenodo

Relying on container dns name resolution is inherently broken. ... 476, [BUG] Campaigns/Location Microservices fail when deployed to Kubernetes cluster #336 ...