DNS & Request Routing
Adventive’s edge is a hybrid: the Enterprise zones front an established AWS platform (application load balancers, CloudFront, S3), while a growing set of hostnames resolve to Cloudflare-native services, Workers, R2, Pages, that carry the newer stack. Cloudflare sits in front of both, providing TLS, caching, and DDoS protection.
Origin classes
Section titled “Origin classes”| Origin | Reached by | Examples |
|---|---|---|
AWS ALB, production-ads (us-east-1) | Proxied CNAME | ads, amp, serve |
AWS ALB, production-console (us-east-1) | Proxied CNAME | api, console, apivast, appvast |
AWS ALB, staging (us-east-1) | Proxied CNAME | admin, ads, api, console on staging |
| AWS CloudFront | Proxied CNAME | auth.* on .com, .dev, staging |
| AWS S3 (website buckets) | Proxied CNAME | assets, html5, video, vod, demo, university |
| Cloudflare R2 | Proxied CNAME → public.r2.dev | media, static, email |
| Cloudflare Pages | Proxied CNAME | docs.adventive.dev |
| Cloudflare Workers | Worker route / custom domain (AAAA 100::) | cms, www, geo, api.dev, status, tools |
| HubSpot | Proxied CNAME | support.adventive.com |
Production, adventive.com
Section titled “Production, adventive.com”Twenty-two records are proxied; the rest are DNS-only. The proxied set divides cleanly into AWS origins, Cloudflare-native origins, and Worker-fronted hostnames.
| Hostname | Type | Origin |
|---|---|---|
ads, amp | CNAME | AWS ALB (ads) |
api, apivast, appvast, console | CNAME | AWS ALB (console) |
console-test | CNAME | AWS ALB (console-test) |
auth | CNAME | AWS CloudFront |
demo, university | CNAME | AWS S3 |
support | CNAME | HubSpot |
media, static | CNAME | Cloudflare R2 |
www, apex, cms, gallery, brandguide, abd, geo-001, plugshare-geo, plugshare-geo-test | AAAA 100:: | Cloudflare Workers (custom hostnames) |
The AAAA 100:: placeholder records are the required marker for a Worker custom hostname. The record must exist before the Worker is bound to that route, or the first request returns a 1014 error. This is a documented Adventive convention.
Asset CDN, adventivecdn.com
Section titled “Asset CDN, adventivecdn.com”Every record is a proxied CNAME to an AWS S3 website bucket, organised by asset type and environment: assets, billing, html5, override, video, and vod, each with -development and -staging variants alongside the production name. Two exceptions front the ads ALB (ads, serve), and email points to R2. A single Worker route, ads.adventivecdn.com/ad*, is served by edgecache-ad-router-production.
Staging, adventivestg.com
Section titled “Staging, adventivestg.com”Thirteen proxied records mirror production against the shared staging load balancer (staging-1267721247.us-east-1), which serves admin, ads, amp, api, apivast, appvast, billing, and console. auth runs on CloudFront, media on R2, and three AAAA 100:: Worker hostnames cover the apex, abd, and cms.
Development, adventive.dev
Section titled “Development, adventive.dev”The development zone is where the Cloudflare-native stack is most visible. Seven Worker hostnames (api, status, admin-api, genesis-admin, nr, productlove, abd) resolve as AAAA 100::; docs points to the Pages project; media to R2; auth to CloudFront; vod to S3; and ads-dev to an EC2 instance (3.93.1.210). The db-aggregate-dev, db-billing-dev, and db-console-dev hostnames, plus tunnel. All CNAME to the adv-cflared-dev tunnel, which is the entry point of the database access chain covered under Zero Trust & Security.
Confirmed Worker routes
Section titled “Confirmed Worker routes”| Zone | Route pattern | Worker |
|---|---|---|
adventive.com | media.adventive.com/brand/signatures/latest-post-title.png | latest-post-title |
adventive.dev | api.adventive.dev/* | adv-svc-public-api-dev |
adventive.dev | status.adventive.dev/* | adventive-status-worker-dev |
adventive.dev | admin-api.adventive.dev/* | adv-svc-admin-api-dev |
adventive.dev | genesis-admin.adventive.dev/* | adv-ui-admin-dev |
adventive.dev | genesis-admin.adventive.dev/api/* | adv-svc-admin-api-dev |
adventive.dev | nr.adventive.dev/* | adv-svc-newrelic-proxy-dev |
adventive.dev | productlove.adventive.dev/* | adv-ui-productlove-dev |
adventive.io | tools.adventive.io/* | adventive-tools-gateway-worker-dev |
adventivecdn.com | ads.adventivecdn.com/ad* | edgecache-ad-router-production |
Marketing and CMS Workers (for example on cms.*) bind via Workers Custom Domains rather than explicit routes, which is why their hostnames appear as AAAA 100:: records with no matching route entry.