Custom Domain Setup

Run your exchange under your own domain. Supply sources (Publishers) send VAST requests to rtb.yourexchange.com, demand sources (DSPs) call api.yourexchange.com, and your dashboard lives at yourname.praevis.com — all proxying transparently to Praevis infrastructure.

DNS records to add

Add these CNAME records at your DNS provider:

TTL: Set to 300 seconds (5 minutes) during setup. Once confirmed working, increase to 3600.

SSL certificates

SSL is managed automatically via Let’s Encrypt on our end. Once your CNAME is live and propagated, HTTPS works within minutes — no certificate upload or renewal required.

TLS version: TLS 1.3 minimum, TLS 1.2 accepted for legacy compatibility.

Verification

After adding your DNS records, verify propagation:

# Check CNAME is pointing correctly
dig CNAME rtb.yourexchange.com
 
# Expected output includes:
# rtb.yourexchange.com. 300 IN CNAME rtb.praevis.com.
 
# Test the endpoint responds
curl https://rtb.yourexchange.com/health
# Expected: {"status":"ok","region":"fra"}

DNS propagation typically takes 2–10 minutes. If you’re still seeing the old record after 30 minutes, flush your local DNS cache:

# macOS
sudo dscacheutil -flushcache
 
# Linux
sudo systemctl restart systemd-resolved

Passing your domain to supply sources

Once your domain is live, supply sources build their VAST tags using your domain:

https://rtb.yourexchange.com/vast?site_id={PUBLISHER_ID}&w={W}&h={H}&ip={IP}&ua={UA}

The site_id Supply Source ID is the same UUID from your partner dashboard — just the domain changes.

Partner ID header

Your supply sources and demand sources are identified by the X-User-Partner-ID header that Praevis adds internally. You don’t need to include this in VAST tags — it’s derived from your custom domain automatically.

For direct API calls (management API), include:

X-User-Partner-ID: {YOUR_PARTNER_UUID}

Your partner UUID is shown in Settings → Partner Info in your dashboard.

Troubleshooting

CNAME not propagating Verify the record is set at the root domain’s nameservers (not a proxy like Cloudflare in proxy mode). If using Cloudflare, set the record to DNS only (grey cloud), not Proxied (orange cloud) — Cloudflare proxying Praevis endpoints causes SSL certificate conflicts.

SSL certificate error Wait 5–10 minutes after CNAME propagation for Let’s Encrypt to issue the cert. If errors persist after 30 minutes, contact [email protected] with your domain name.

Health endpoint returns 404 The CNAME is resolving but the domain isn’t registered in our system yet. Contact [email protected] — we need to add your domain to the partner configuration.