Container Registry
Container Registry
Container Registry
Document
Container Registry (CR)
What's new
Overview
Billing
Billing item
Getting started
User guide
User authorization
Authorization management
Robot account management
Instance management
Namespace management
OCI artifact repository management
OCI artifact management
Version management
Tag immutability rule management
Tag retention rules management
Access configuration
Access control
Distribution acceleration
P2P acceleration
Image lazy loading
Registry replication
Audit log management
Alerts and notifications
Best practices
Image push and pull
Image migration and synchronization
DevOps delivery
FAQ
Authorization
VPC
Image push and pull
Limits
Registry replication
P2P acceleration
Access control
API
Calling Method
Instance Management
Namespace Management
OCI Artifact Repository Management
OCI Artifact Version Management
Domain Management
Access Endpoint Management
Temporary Access Key
Robot Account Management
General Data Structure
Artifact repository AR
What's new
Product overview
Getting started
User guide
Instance management
Repository Management
Access control
Permanent access credentials
Temporary access credentials
Maven package management
Generic package management
PyPI package management
NPM package management
Uploading packages
Downloading packages
AI package management
Permission management
API Reference
Repository Management
Package management
Version Management
File Management
Temporary Key Management
General Data Structure
- Documentation
Container RegistryContainer Registry (CR)FAQAccess controlWhy does the domain name of a CR instance fail to resolve?
Copy page
Download PDFAccess control
Why does the domain name of a CR instance fail to resolve?
Copy pageDownload PDFWhy does the domain name of a CR instance fail to resolve?
Issue description
When I access a Standard Edition instance over the public network, the domain name may fail to resolve. The following no such host error message is returned.
dial tcp: lookup *****.cr.****.com on ****: no such host
Cause
- Public network access is not enabled.
- DNS resolution may not take effect immediately after public network access is enabled. DNS resolution usually takes 3 to 5 minutes after public network access is enabled.
Solution
- Ensure that public network access is enabled. For details, see Enabling public network access.
- After public network access is enabled, allow 3 to 5 minutes for DNS resolution before accessing the domain name of the Standard Edition instance.
Last updated: 2026.10.19 15:46:50
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
