This topic answers frequently asked questions about adding domain names in ApsaraVideo Live.
Why does ApsaraVideo Live require domain name ownership verification?
Domain name ownership verification prevents unauthorized use. Without it, any user could add a domain name that belongs to someone else, causing conflicts and security risks. Verification ensures that only the verified owner of a domain name can add it to ApsaraVideo Live. For instructions, see Verify the ownership of a domain name.
Is domain name ownership verification required for each Alibaba Cloud account that adds a domain name to ApsaraVideo Live for the first time?
Yes. Each Alibaba Cloud account is treated as a distinct user, so domain name ownership verification is required the first time each account adds a domain name to ApsaraVideo Live.
Can I delete the DNS record or verification file after passing domain name ownership verification?
Yes. The DNS record or verification file is only used to verify domain name ownership. Once verification passes, you can delete it.
Is ownership verification required for a domain name that has already been added to ApsaraVideo Live?
No. If you add the domain name demo.aliyundoc.com to ApsaraVideo Live and its CNAME assignment works as expected, you are considered the owner of aliyundoc.com. Any subdomain of aliyundoc.com that you add later—such as learn.aliyundoc.com and guide.aliyundoc.com—does not require separate ownership verification.
Is ownership verification required when I call the AddLiveDomain operation to add a domain name to ApsaraVideo Live?
Yes. The verification process is the same as adding a domain name through the ApsaraVideo Live console. Before calling the AddLiveDomain operation, add a DNS record or upload a verification file to the root directory of your origin server.
What do I do if domain name ownership verification fails after I add a DNS record or upload a verification file?
Submit a ticket for manual verification. Include the reason for the failure and provide evidence of domain name ownership. For details, see Contact us.
Why does the console still show the CNAME as not configured after I configure it?
CNAME resolution usually takes 10 to 30 minutes to take effect. The console monitors the CNAME status periodically, so the displayed status lags behind the actual state. A status of not configured does not affect actual use. To check whether resolution has taken effect, run nslookup -type=cname <your domain name>. After resolution is correct, stream ingest and stream pulling work as expected.
What do I do if a streaming domain cannot be deleted because an association exists?
You cannot delete a streaming domain while a mapping between the streaming domain and an ingest domain exists. Remove the domain name mapping first by calling the DeleteLiveDomainMapping operation, and then delete the streaming domain. An ingest domain and a streaming domain must reside in the same region, which is the same live center, before you can create a mapping between them.
How do I update an expired domain name certificate that breaks HTTPS playback?
After a certificate expires, HTTPS stream ingest and stream pulling fail. Replace the certificate in HTTPS certificate configuration of domain name management, or renew the certificate in Certificate Management Service and then deploy it again. The new certificate takes effect about 5 minutes after deployment.
I have only one ICP-filed primary domain name. How do I add ingest and streaming domains?
You do not need a separate ICP filing for a subdomain. Add subdomains under the primary domain name that already has an ICP filing. For example, use push.example.com as the ingest domain and pull.example.com as the streaming domain. Complete domain name ownership verification and CNAME resolution for each subdomain. If you do not own a domain name yet, register one and complete ICP filing first.
How do I configure DNS records after I migrate from another cloud provider?
After migration, configure DNS records again in your DNS service instead of reusing the records from your previous provider. Note the following key points:
-
Add a separate CNAME record for the ingest domain and for the streaming domain. Use the CNAME that the console assigns to each domain name. The two domain names cannot share the same target value.
-
If you used a TXT record for domain name ownership verification, you can delete the record after verification passes. You must keep the CNAME records permanently.
-
If your workloads involve other accelerated domain names, such as domain names for video-on-demand or static resources, configure each domain name separately. A single missing record breaks part of the delivery path.
After you finish the configuration, verify that resolution has taken effect in the domain name configuration wizard or the self-service troubleshooting tool in the console, or by running nslookup -type=cname <your domain name>. Complete the configuration on the new platform and confirm that stream ingest and stream pulling work before you switch production traffic over.
Why am I prompted that the parameter is invalid when I add a callback URL?
A callback URL must be an HTTP or HTTPS address that is accessible over the Internet. ApsaraVideo Live validates the format and the reachability of the address when you submit it. Validation fails if the address is a private address, such as an address in the 192.168 or 10. ranges, if the address is localhost, if the protocol prefix is missing, or if the address contains invalid characters. Deploy the service that receives callbacks on a server that has a public address, and make sure that ApsaraVideo Live can reach that server. Before you submit the configuration, request the address once from outside your network with a browser or the command line to confirm that it is reachable.