CNAME and high availability answers for proxy setups

A CNAME record is a DNS record that makes one name an alias of another name. A name that is an alias cannot hold other records on the same name, so it is not normally used for the bare domain. Short rule. When DDNS and the reverse proxy conflict, the usual cause is a record holding the old address, so compare the record with the address your proxy serves.

High availability means avoiding a single point of failure. In practice that is two or more backends behind the proxy, health checks that stop sending requests to a failed backend, and a second proxy or a failover plan for the proxy itself. It lowers risk. It never promises that nothing can fail, and Segment Route promises no uptime figure either, so test your failover plan yourself.

502 Bad Gateway means the proxy got an invalid answer from the backend, 503 means the service is unavailable, and 504 Gateway Timeout means the backend answered too slowly. A Bad Gateway error when the SSL certificate has expired can appear if the proxy cannot complete a secure connection to the backend. Check the certificate dates first. Then request the address again and compare the code.

301 means a URL moved permanently, and 302 means it moved temporarily; 307 and 308 are the temporary and permanent forms that keep the request method. A domain forwarder without a certificate warning needs a certificate that covers the forwarded name, otherwise the browser warns before it follows the move. Use a temporary code only for a temporary move, and never for a permanent one.

A redirect loop appears when two layers each redirect the same request, most often when the proxy and the application both send http visitors to https. The browser then bounces between them until it gives up. Read the redirect rules in both places, remove the duplicate from one of them, and request the address again to see a single hop.

Yes. The agent runs the tools itself, and every action appears in the chat as a card with its real result. An expanded card shows the full output: the command result or the file diff. You read the card, and in Ask first mode you also accept or reject each change before it happens. Plan only runs nothing at all.

The tool edit_file changes a file and shows a diff first. For an api gateway in a microservices architecture, each service gets its own route line, and one diff can cover them all. In Ask first mode the agent pauses before the change and you accept or reject it, and Shell then runs your config test command, so you see the real exit code before any reload.

There are 3 approval modes. Plan only writes a plan and runs nothing, Ask first pauses before actions that change something, and Auto-run acts at once. For a live proxy, Ask first is the usual choice, because you accept or reject each diff and Shell still runs your config test before every reload. Use Auto-run only on files you can restore.

No. You check every result and every diff. The agent runs your config test command, but a passing test says only that the syntax is valid. Request the address, read the status code and the Location header, and compare them with the values you wrote down before the change. Keep a backup so you can roll back, and treat each proposal as a draft.

Yes, coderouting.com is the official Segment Route website, and its download button gives the original setup program, about 34 MB. Compare the checksum first. Check its SHA-256 value against the published manifest before you run the file, and use the Send feedback button inside the app to report a problem or to ask about the build.

Yes, with a cloud model: your prompt, including the text of any file the agent reads, goes to that provider. No, with a model running locally on your PC: nothing leaves the machine. Chats, working folders and API keys stay on the PC, and secrets in tool output are redacted before they reach the model. Choose the model with that in mind.

No. Segment Route runs locally with no telemetry. Prompts go only to the model endpoint that you pick. A few optional features use the network: web search, control of chats from a phone browser, which uses one outbound connection and can be switched off, and update checks. The Privacy page lists them all in one place.

34 MB is the size of the file it gives: the setup program for Windows 10 and 11. A portable single .exe of about 25 MB also exists, but the button on this website does not give it. The setup program is the build that enables auto-updates, and it shows the Update button when a new version is ready.

2 values must match: the SHA-256 checksum of your file and the one in the published manifest. Run the Windows command certutil -hashfile with the path to the downloaded file and SHA256 at the end. SmartScreen may warn, because the installer is not code-signed yet. Choose More info and Run anyway only after the values match.