From 5fe51f33027064203f90dad8c39da3de55a165ce Mon Sep 17 00:00:00 2001 From: zaher-abb-vw Date: Fri, 24 Jul 2026 15:04:57 +0200 Subject: [PATCH] docs: add curl --resolve fallback for nip.io DNS issues in controlplane quick start Some local resolvers (observed on macOS) fail to resolve *.nip.io hostnames, causing 'curl: (6) Could not resolve host' during Step 6 verification. Document curl's --resolve flag as a per-request workaround, and an /etc/hosts entry as a persistent fix covering the openstack CLI commands as well. --- docs/quick-start-controlplane.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/quick-start-controlplane.md b/docs/quick-start-controlplane.md index 851678ea9..106e93f08 100644 --- a/docs/quick-start-controlplane.md +++ b/docs/quick-start-controlplane.md @@ -387,6 +387,32 @@ at `https://keystone.127-0-0-1.nip.io:8443/v3` — the same path as the per-serv curl -k https://keystone.127-0-0-1.nip.io:8443/v3 ``` +::: tip If your host cannot resolve `*.nip.io` +Some local resolvers (observed on macOS) fail to resolve `nip.io` hostnames, +which surfaces as `curl: (6) Could not resolve host`. Force the hostname to +resolve to the loopback address for a single request with `curl`'s +`--resolve`: + +```bash +curl -k --resolve keystone.127-0-0-1.nip.io:8443:127.0.0.1 \ + https://keystone.127-0-0-1.nip.io:8443/v3 +``` + +`--resolve ::` overrides DNS for that host/port pair only — +`curl` still sends the original hostname in the request and TLS handshake, but +connects directly to `127.0.0.1`. For a fix that also covers the `openstack` +CLI commands below (which do not support `--resolve`), add loopback entries to +`/etc/hosts` instead: + +```bash +sudo sh -c 'cat >> /etc/hosts <