liveBook · Manning

Cname record

As explained in Build Python Web Apps with Streamlit

A CNAME record is a DNS record that aliases one domain name to another domain name.

A CNAME record is a DNS entry that aliases one domain name to another address. It lets a browser reach a deployed app through a custom domain instead of its provider-generated address. section 12.4.1

Pointing a custom domain to an app

In a DNS provider such as Cloudflare, add a record with Type CNAME, Name www, and Target fact-frenzy.us-east-2.elasticbeanstalk.com. Disable proxying or forwarding initially. DNS changes may take several minutes to an hour to propagate. section 12.4.1

www.factfrenzyapp.com -> fact-frenzy.us-east-2.elasticbeanstalk.com

Follow the concrete alias from www.factfrenzyapp.com to its Elastic Beanstalk target. section 12.4.1

CNAME records can also validate domain ownership for a public certificate. Add the name and value supplied by AWS to DNS; after validation, the certificate changes from Pending Validation to Issued. section 12.4.2

How Build Python Web Apps with Streamlit covers it

How deep it goes
Defines the record and demonstrates DNS-provider fields, propagation delays, proxy settings, and certificate validation.
Examples
Uses www.factfrenzyapp.com, an Elastic Beanstalk hostname, Cloudflare fields, and AWS-generated validation entries.
What it assumes
Assumes access to a registered domain, a DNS-management dashboard, and a deployed Elastic Beanstalk application.
What you can do after
Operate/configure Cloudflare DNS to route a custom domain and prove ownership for AWS certificate issuance.
How it connects
Connects DNS, domain names, Elastic Beanstalk, Streamlit deployment, public certificates, and domain ownership validation.

Also explained in

Compare how 2 books explain cname record →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build Python Web Apps with Streamlit. The section links point to the parts of the book it draws on.