dns

TGI service unreachable during benchmark due to DNS resolution failure

by
white printer paper on white textile

Problem – TGI Service Unreachable During Benchmark During automated performance benchmarking of a Text Generation Inference (TGI) deployment, the benchmark script repeatedly fails with a DNS resolution error: 2026-10-18 14:32:07,123 ERROR benchmark.py: Failed to resolve host “tgi-model-prod.example.com”: Name or service not known Traceback (most recent call last): File “/opt/benchmark/benchmark.py”, line 87, in run ip = … Read more

Sandbox cannot resolve ChromaDB host DNS during vector store init

by
photo of computer cables

Problem During development in a sandbox environment the application fails to initialise the ChromaDB vector store. The client library throws a DNS resolution error and aborts before any HTTP request is sent. Observed log excerpt: 2026-10-07 14:22:31,842 ERROR chromadb.client – Failed to resolve host ‘chroma-db.internal.svc.cluster.local’: Name or service not known Traceback (most recent call last): … Read more

MLflow tracking server run registration fails due to DNS lookup error

by
cable network

Problem: MLflow Tracking Server Fails to Register Runs Due to DNS Lookup Errors When a client attempts to start a new run, the tracking server raises an exception similar to: socket.gaierror: [Errno -2] Name or service not known mlflow.exceptions.MlflowException: Unable to register run Traceback (most recent call last): … urllib3.exceptions.NewConnectionError: Failed to establish a new … Read more

Milvus vector index loading fails with intermittent DNS resolution timeouts

by
brown and black bird flying under white clouds during daytime

Milvus Vector Index Loading Fails with Intermittent DNS Resolution Timeouts Problem Statement In edge deployments where Milvus runs on resource‑constrained nodes (Raspberry Pi, Jetson, etc.), the vector index loading phase intermittently hangs. The underlying symptom is a DNS resolution failure for the Etcd and MinIO service endpoints, which manifests as: Log entries such as 2023/07/15 10:12:34 … Read more

Docker container DNS resolution fails intermittently in multi-region Kubernetes

by
red and blue cargo ship on sea during daytime

Problem – Intermittent DNS Resolution Failures in Docker Containers Across Multi‑Region Kubernetes AI inference services deployed as Docker containers on Amazon EKS clusters in several AWS regions (e.g., us-east-1, eu-central-1, ap-south-1) experience sporadic failures when resolving external endpoints such as model registries, third‑party APIs, or telemetry services. The failures manifest as: Go errors: dial tcp: … Read more

LangChain DNS resolution failure during batch API calls

by
cable network

Problem – DNS resolution failures during LangChain batch API calls When running a LangChain batch pipeline on a distributed compute cluster (Kubernetes, Ray, Azure Batch, or on‑premise HPC), the jobs intermittently abort with DNS‑related exceptions. Typical log excerpts look like: socket.gaierror: [Errno -3] Temporary failure in name resolution aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host api.example.com:443 ssl:default … Read more

GCP Compute Engine intermittent DNS resolution failure

by
a rack of servers in a server room

Problem – Intermittent DNS Resolution Failures on GCP Compute Engine In a multi‑region AI training pipeline, Compute Engine instances in us-central1 and europe‑west1 rely on internal DNS names such as ml‑worker-01.c.my‑project.internal to exchange model checkpoints. During peak synchronization windows the following symptoms were observed: Python training workers raised socket.gaierror: [Errno -3] Temporary failure in name … Read more