Use curl --resolve and --connect-to to test DNS and proxy boundaries

For curl --resolve vs --connect-to, the safest approach is a bounded operational change, not a command pasted without context. This runbook starts with effective state, shows the smallest candidate action, and finishes by repeating the real user or system path.

TL;DR: --resolve supplies an address for a host and port while retaining the URL host for TLS and HTTP; --connect-to changes the network destination without rewriting application authority. Capture a baseline with curl -v --connect-timeout 5 https://app.example.com/, make the reviewed change only when the evidence matches, then verify with getent hosts app.example.com and keep the rollback ready.

Audience: operators who understand IP addresses and ports and can capture bounded network evidence without collecting payloads unnecessarily. This guide assumes familiarity with Linux networking and a change window appropriate to the system.

The direct answer

The override reaches the intended address while TLS SNI and Host remain the production name. That is the success condition for curl --resolve vs --connect-to; command completion by itself is not enough.

The important boundary is name resolution, route selection, neighbor reachability, firewall policy, transport state, and application listener. --resolve supplies an address for a host and port while retaining the URL host for TLS and HTTP; --connect-to changes the network destination without rewriting application authority. If an observation does not identify which side of that boundary failed, collect a narrower observation before changing state.

How the mechanism works

For curl --resolve vs --connect-to, use this mental model: a connection moves from a name to an address, through route and policy lookup, into a transport socket, and finally to the process bound to the selected address and port. The model prevents a common mistake—treating configuration text, control-plane acceptance, process state, and end-user behavior as the same proof.

Follow four stages:

1. Observe: identify the exact host, object, version, owner, and active configuration.
2. Interpret: write the expected result, the abnormal result, and what would remain inconclusive.
3. Change: apply one reviewed action at the narrowest layer that contradicts the baseline.
4. Verify: repeat the original path and compare the same evidence, including adjacent safety controls.

Preflight and safety boundary

Preserve a second management path before changing routes, resolver state, interfaces, or firewall rules, and redact payloads and private topology from captures.

Before curl --resolve vs --connect-to, record UTC time, the current version or digest, the exact target, recent changes, and who owns the workload. The rollback for this runbook is: remove the exact hosts-file line, flush only relevant caches if necessary, and retest normal resolution.

Do not continue if the target identity is ambiguous, the current state cannot be saved, the only recovery session would be at risk, or the proposed command affects more objects than the brief names.

Capture the read-only baseline

Run these commands one at a time. Replace example names and addresses deliberately; do not paste production secrets into a transcript.

curl -v --connect-timeout 5 https://app.example.com/
curl -v --resolve app.example.com:443:192.0.2.20 https://app.example.com/
curl -v --connect-to app.example.com:443:192.0.2.20:443 https://app.example.com/

Interpret the baseline before moving on:

• Expected: the override reaches the intended address while TLS SNI and Host remain the production name.
• Abnormal: the direct backend fails too, or succeeds only when proxy, DNS, or load-balancer behavior is bypassed.
• Inconclusive: missing output can also mean the wrong context, permissions, namespace, log window, binary, or target. Prove those assumptions before treating absence as health.

Save the decisive output, exit status, and timestamp. Redact credentials, customer data, private topology, tokens, and complete environment dumps.

Apply the smallest candidate change

The following is state-changing example syntax, not an instruction to run it unchanged:

sudo sh -c 'printf \"%s\
\" \"192.0.2.20 app.example.com\" >> /etc/hosts'

For curl --resolve vs --connect-to, the proposed change is acceptable only when the read-only baseline predicts its effect and the rollback is available. The key risk is: a persistent hosts-file override can silently pin production traffic to one instance after the test.

Prefer an immutable artifact, validated configuration, dry-run, transaction, candidate object, or staged target when the tool supports one. Record the exact command and UTC time so later telemetry can be correlated to the change.

Verify the result from the outside in

getent hosts app.example.com
curl -v https://app.example.com/
openssl s_client -connect 192.0.2.20:443 -servername app.example.com </dev/null

Verification for curl --resolve vs --connect-to has three layers:

1. The control plane or command reports the intended effective state.
2. The process, resource, or data path reflects that state without a new pressure signal.
3. The original user-visible or dependent-system path succeeds from an independent vantage point.

If getent hosts app.example.com succeeds but the original path still fails, stop. The change may have repaired a local symptom while DNS, policy, routing, caching, dependency, or client state remains broken.

Failure branches

The baseline does not match this runbook

When the direct backend fails too, or succeeds only when proxy, DNS, or load-balancer behavior is bypassed, do not force the candidate command. Return to identity and scope, compare a healthy peer only through effective settings, and name a new falsifiable mechanism.

The change succeeds but behavior does not

A successful sudo sh -c 'printf \"%s\ proves that one interface accepted a request. It does not prove convergence, readiness, data compatibility, external routing, or client recovery. Re-run the same evidence at each downstream boundary.

The change makes the system worse

Execute the written rollback: remove the exact hosts-file line, flush only relevant caches if necessary, and retest normal resolution. Preserve the failed candidate and relevant logs long enough to explain the outcome; do not destroy the evidence with broad cleanup or repeated restarts.

Operator checklist

• Confirm the exact target, context, identity, version, and active owner.
• Capture the read-only baseline and one disconfirming observation.
• Label sudo sh -c 'printf \"%s\ as state-changing during review.
• Keep recovery access and rollback independent of the path being edited.
• Change one layer, record UTC time, and wait for its real convergence boundary.
• Verify the original path, adjacent controls, resource pressure, and persistence.
• Update the runbook when observed behavior differs from the source-reviewed model.

Investigate it in Tryssh

$ getent hosts app.example.com
Expected: the override reaches the intended address while TLS SNI and Host remain the production name.

Tryssh can preserve this evidence loop and show a state-changing command for human approval. It does not make the operator's identity, recovery access, rollback, or platform authority decisions.

Evidence and review status

This curl --resolve vs --connect-to runbook was source-reviewed on 2026-07-29 against current first-party documentation. The commands are illustrative and use example targets. The page does not claim that the change was reproduced across every distribution, managed service, version, network, or workload.

Limitations and trade-offs

A persistent hosts-file override can silently pin production traffic to one instance after the test. Managed platforms may generate configuration, restrict privileges, replace local state, or expose a different control plane than the upstream project. Confirm the installed version and provider contract before applying a repair.

Search visibility is not proof of operational correctness. Treat this page as a decision aid, preserve independent recovery, and stop when the evidence contradicts its assumptions.

Related operator runbooks

Continue with Linux conntrack table, systemd-resolved troubleshooting, the Linux networking foundation guide, and the SSH hardening checklist.

Sources and further reading

• Curl --resolve vs --connect-to first-party reference
• Linux kernel networking documentation
• ss manual
• ip-route manual