Help Center/
Content Delivery Network/
FAQs/
Domain Name Settings/
Why Do My Domain Requests Still Go to CDN PoPs After My Domain Name Has Been Disabled and Domain Resolution Has Been Changed?
Updated on 2024-08-15 GMT+08:00
Why Do My Domain Requests Still Go to CDN PoPs After My Domain Name Has Been Disabled and Domain Resolution Has Been Changed?
Possible causes:
- Carriers and users have cached the DNS resolution result locally. Before the cache expires, domain requests are still sent to CDN PoP. They will be resolved to the new DNS record only after the cache expires.
- Before the domain name is disabled, a user pings the domain name to obtain the IP addresses of CDN PoPs, and then binds the domain name with the PoP IP addresses in the local hosts file. It means that the user specifies a resolution to bypass normal DNS resolution. As a result, requests from the user are sent to CDN PoPs.
Solutions:
- If the problem is caused by local cache, wait until the cache expires.
- If a user binds the domain name with CDN PoPs in the local hosts file, the user needs to unbind them.
Parent topic: Domain Name Settings
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot