Under 30 seconds from DNS record to live HTTPS
22 seconds end to end (timed on a test hostname in a zone on FastDog’s own nameservers, every step run by our operator from scripts). An independent time-keeping app and a FastDog customer. Its domain was registered through FastDog Domains, one hostname is attached with a CNAME, and it serves over HTTPS through the FastDog edge and tunnel.
How we measured: on 2026-10-09 we ran the same attach flow on a throwaway test hostname and timed each step. DNS record to a valid HTTPS response took 22 seconds. Every step was run from scripts by our operator, including the TLS step, which is operator-assisted in Phase 1. Your own time to add a CNAME at your DNS host and start the agent comes on top.
Attach flow, 2026-10-09.
DNS record
CNAME to
attach.fastdognetworks.comadded; both nameservers answering 8.7 s later.Attach hostname
Hostname attachment created (0.9 s).
Verify
CNAME verified and a hostname-bound agent credential issued (2.8 s).
Run agent
Agent started beside a test origin and connected outbound to the edge (within 4.0 s).
Operator TLS step
Site block added on the edge, validated, and reloaded (1.1 s).
HTTPS live
Let’s Encrypt certificate obtained; a request from outside the edge returned 200 with a valid certificate (4.8 s).
The test hostname, its DNS record, credential, certificate, and agent were removed afterwards.
Hostname attach. DNS kept in place.
The customer’s app hostname is a CNAME to attach.fastdognetworks.com. The domain’s nameservers were not moved to FastDog.
app.usepunchclock.com. CNAME attach.fastdognetworks.com.The app serves over HTTPS through the FastDog edge and tunnel, and its www hostname redirects to the app.
Elapsed time for this customer, registration to HTTPS on the edge: 11 h 12 min (05:32 → 16:44 UTC, 2026-10-08). Most of that was overnight, before the hostname was attached.
Tell us what
you run.
Start with your hostname, where your DNS lives, and where the origin runs.
support@fastdognetworks.com