> For the complete documentation index, see [llms.txt](https://www.axisnow.io/zh/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.axisnow.io/zh/docs/edge/endpoints/origin-address.md).

# 源地址

一组带权重的回源地址及其健康检查与观测

源地址（Origin）是一组回源目标：一个或多个 IP 或域名，各带权重，配置一次即可被多个域、TCP 转发和[回源控制](/zh/docs/edge/policies/upstream-control.md)规则引用。在域或 TCP 转发里直接填写的地址会自动创建为同名的源地址。健康检查和回源洞察都挂在源地址上。

## 地址与权重 <a href="#addresses" id="addresses"></a>

* **地址**：IPv4 或域名。域名在每个边缘上解析，解析出的每个 IP 都是一个独立的回源目标，按 DNS 记录的 TTL 重新解析，最短 30 秒、最长 120 秒。
* **权重**：1–100，默认 10，请求按权重比例在地址间加权轮询分配。域名条目解析出的各个 IP 等权参与，不按条目上的权重分配，列表和表单显示的百分比对域名条目不准确。
* **剔除**：健康检查判定异常的地址在剔除时长内不再分配请求，全部地址都被剔除时回退到第一个地址继续回源。

同一个源地址里不要混填域名和 IP，两者的权重口径不同，比例不可控。

## 健康检查 <a href="#health-check" id="health-check"></a>

每个边缘独立判断每个地址的健康状态。真实流量监测始终开启，从回源失败中识别异常；主动 TCP 探测可选，用于剔除后的恢复确认。只有地址数大于 1（含域名解析出多个 IP）时才会发生剔除，单个地址的源地址由[回源重试](/zh/docs/edge/policies/upstream-control/configuration.md#retry)兜底。机制见[健康检查](/zh/docs/edge/endpoints/origin-address/health-check.md)。

## 引用与删除 <a href="#references" id="references"></a>

列表可勾选显示**被引用**列，或在行菜单查看引用该源地址的域、TCP 转发和规则。被引用的源地址不能删除；修改地址或健康检查后对所有引用方同时生效。

## 下一步 <a href="#next-steps" id="next-steps"></a>

<table data-search="false"><thead><tr><th width="160">页面</th><th>内容</th></tr></thead><tbody><tr><td><a href="/zh/docs/edge/endpoints/origin-address/health-check.md">健康检查</a></td><td>两种信号如何判定、剔除与恢复、计数的范围</td></tr><tr><td><a href="/zh/docs/edge/endpoints/origin-address/insight.md">洞察与日志</a></td><td>列表的 24 小时回源趋势，洞察页的指标与健康检查事件</td></tr><tr><td><a href="/zh/docs/edge/endpoints/origin-address/best-practices.md">最佳实践</a></td><td>地址数量、探测、剔除时长与发布维护</td></tr><tr><td><a href="/zh/docs/edge/endpoints/origin-address/faq.md">常见问题</a></td><td>没有剔除、剔除后仍有流量、只有剔除没有恢复的排查</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.axisnow.io/zh/docs/edge/endpoints/origin-address.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.