BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VTIMEZONE
TZID:America/Chicago
BEGIN:STANDARD
DTSTART:20001029T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:20260711T094656Z - 36275@25e1d5f22592
DTSTART;TZID=America/Chicago:20250812T120000
DTEND;TZID=America/Chicago:20250812T130000
CREATED:20260711T094656Z
DESCRIPTION:<a href="https://customdomain.ai/event/from-dns-to-live-https-t
 he-whole-path-17">From DNS to Live HTTPS\, the Whole Path</a>\nIf your pla
 tform lets customers bring their own domain\, you already know the setup i
 s where things get messy. DNS records land in the wrong place\, ownership 
 checks stall\, and certificates expire at the worst possible moment. This 
 session is a technical walkthrough for the engineers who own that path. We
  will follow a single customer domain from an empty DNS record all the way
  to live traffic served over HTTPS\, and we will look at what has to be tr
 ue at each step for it to hold up in production.What you will learnHow DNS
  configuration\, domain ownership verification\, and TLS certificate issua
 nce fit together into one connected flow rather than three separate chores
 .Three ways a domain can be connected: one click provider authorization\, 
 a provider API token\, and a guided manual flow that verifies automaticall
 y.How a control plane and an edge split the work\, with the edge terminati
 ng TLS and routing traffic while certificates are issued and renewed on de
 mand.What strict multi tenant isolation looks like in practice\, so one cu
 stomer domain never reaches into another.Why a domain can go live in about
  30 seconds\, and what your users experience while that happens.Who this i
 s for This walkthrough is built for platform and infrastructure engineers 
 who carry the pager for custom domains. If you have wired up ACME clients\
 , chased propagation delays\, or built the onboarding screen where custome
 rs paste in DNS records\, you are the audience we wrote this for.What we w
 ill coverThe full path of a single domain\, from the first DNS record to l
 ive HTTPS\, with each checkpoint called out.The three connection methods a
 cross 63 DNS and registrar providers\, and when each one is the right fit 
 for your users.The control plane and edge architecture\, including how TLS
  termination and on demand certificate issuance and renewal work.Multi ten
 ant isolation and the failure cases it is designed [...]
DTSTAMP:20260711T094656Z
LOCATION:Custom Domain
SUMMARY:From DNS to Live HTTPS\, the Whole Path
X-ALT-DESC;FMTTYPE=text/html:<a href="https://customdomain.ai/event/from-dn
 s-to-live-https-the-whole-path-17">From DNS to Live HTTPS\, the Whole Path
 </a>\nIf your platform lets customers bring their own domain\, you already
  know the setup is where things get messy. DNS records land in the wrong p
 lace\, ownership checks stall\, and certificates expire at the worst possi
 ble moment. This session is a technical walkthrough for the engineers who 
 own that path. We will follow a single customer domain from an empty DNS r
 ecord all the way to live traffic served over HTTPS\, and we will look at 
 what has to be true at each step for it to hold up in production.What you 
 will learnHow DNS configuration\, domain ownership verification\, and TLS 
 certificate issuance fit together into one connected flow rather than thre
 e separate chores.Three ways a domain can be connected: one click provider
  authorization\, a provider API token\, and a guided manual flow that veri
 fies automatically.How a control plane and an edge split the work\, with t
 he edge terminating TLS and routing traffic while certificates are issued 
 and renewed on demand.What strict multi tenant isolation looks like in pra
 ctice\, so one customer domain never reaches into another.Why a domain can
  go live in about 30 seconds\, and what your users experience while that h
 appens.Who this is for This walkthrough is built for platform and infrastr
 ucture engineers who carry the pager for custom domains. If you have wired
  up ACME clients\, chased propagation delays\, or built the onboarding scr
 een where customers paste in DNS records\, you are the audience we wrote t
 his for.What we will coverThe full path of a single domain\, from the firs
 t DNS record to live HTTPS\, with each checkpoint called out.The three con
 nection methods across 63 DNS and registrar providers\, and when each one 
 is the right fit for your users.The control plane and edge architecture\, 
 including how TLS termination and on demand certificate issuance and renew
 al work.Multi tenant isolation and the failure cases it is designed [...]
END:VEVENT
END:VCALENDAR