0041-00000106

Problem description

OSS cannot resolve the origin server domain name to an IP address when processing a mirroring-based back-to-origin request.

Causes

The domain name configured in your mirroring-based back-to-origin rule fails to resolve for one of the following reasons:

• The domain does not exist or has no DNS A record. The hostname is not registered, has expired, or has no A record pointing to a valid IP address.

• The domain is an internal or private hostname. OSS fetches objects from the public internet. Internal hostnames (such as internal.example.corp) are not reachable from OSS's network.

• The origin server field contains a protocol prefix or path. The field accepts only a bare hostname or IP address. Values like https://example.com or example.com:8080/path cause resolution failures.

• The CNAME chain is broken. If the domain uses a CNAME record, the target domain must also resolve to a valid IP address.

• The hostname contains a typo. A single incorrect character prevents resolution.

Examples

None

Solutions

1. Confirm the domain resolves publicly. Use a DNS lookup tool such as dnschecker.org to verify the domain resolves to a valid IP address from multiple locations — not just from your local network.

2. Check the origin server field format. The field accepts only the following formats:

   Format	Example
   Bare hostname	example.com
   Hostname with port	example.com:8080
   IPv4 address	203.0.113.10
   IPv4 address with port	203.0.113.10:8080

   Do not include a protocol prefix (http:// or https://) or a path component.

3. If the domain resolves on your local machine but not via the DNS lookup tool, the domain is an internal hostname. Switch to a publicly resolvable domain name or use an IP address instead.

4. After correcting the domain name, update the mirroring-based back-to-origin rule in the OSS console and trigger a new back-to-origin request to verify the fix.

References

Mirroring-based back-to-origin