Use this guide when the Bandwango → Domains page shows Success, but:
You see website issues (such as NXDOMAIN, Too Many Redirects, or similar errors) when you try to load a pass.
Embedded content (e.g. signup card) has disappeared — this happens because all embedded content is hosted by the subdomain, and if that subdomain breaks, embedded items and passes will stop loading.
If Bandwango shows “Success” but content fails, your CNAME record was likely removed or altered. Restore the correct DNS record to fix this.
What “Success” on the Domain Page actually means
Success confirms the subdomain worked previously and the certificate (ACM) is/was valid.
It does not live‑check your current DNS. If the CNAME record was changed or removed later, the Bandwango page can still say Success while your site is down.
Symptoms that point to a DNS issue
Mobile Pass is inaccessible and the browser shows:
NXDOMAIN / “This site can’t be reached / ERR_NAME_NOT_RESOLVED.”
Too Many Redirects (redirect loop).
Certificate/HTTPS warnings when opening the pass.
...or embedded content disappears such as:
Signup cards disappearing from partner or client websites.
Embedded content missing on partner or client websites.
If you see any of the above, continue below.
⚙️ Fix in 6 steps
1) Confirm the problem is DNS-related
Open your subdomain – go.yoursite.com – or your mobile pass in a Private or Incognito window. If you see one of the errors above, proceed.
2) Get the correct DNS target from Bandwango
Log in to Bandwango Experience Builder.
Go to Settings → Domains.
Find your subdomain and copy the DNS target (looks like a long hostname like
word1-word2-randomtext123abc.herokudns.com).
Keep this target handy. You’ll paste it into your DNS provider in the next step.
3) Check your DNS provider and restore the CNAME
Go to your domain’s DNS host (registrar or DNS service like Cloudflare, GoDaddy, Route 53, etc.). For the affected subdomain (example: passes.yourcity.com):
There should be exactly one CNAME record for that host.
Host/Name: usually just the subdomain label (e.g., passes). Some providers expect the full name (passes.yourcity.com).
Value/Target: paste the exact DNS target you copied from Bandwango. Do not include http:// or https://. No extra spaces or trailing dot.
Remove any conflicting A or AAAA records for the same host. You should not have both CNAME and A/AAAA for one host.
Remove any URL forwarding/redirect records for that host.
If you use Cloudflare:
Set Proxy status = DNS only (grey cloud) for this CNAME.
Remove Page Rules/Redirect Rules for this host while testing.
4) Save the DNS changes
Most providers apply changes quickly, but it can vary. After saving, continue to Step 5 to verify that the CNAME is active.
5) Verify the fix
Open the subdomain again in a Private/Incognito window.
Optional (for a quick double‑check): use any DNS lookup tool to confirm the subdomain now resolves to your Bandwango DNS target as a CNAME.
You should no longer see NXDOMAIN/redirect errors. The site, embeds, and mobile pass should load normally.
6) Prevent it from breaking again
Note who manages DNS and lock down changes to the subdomain host.
Document the exact CNAME target inside your team’s runbook.
What to send Support if you still see problems
If you’ve completed the steps and it’s still not working, share:
Your subdomain (e.g., passes.yourcity.com).
A screenshot of the CNAME record (host and target visible).
The exact browser error (NXDOMAIN, Too Many Redirects, item card missing, etc.).
Your DNS provider (e.g., Cloudflare/GoDaddy/etc.).
This will help Support pinpoint the remaining issue quickly.