BahriyaBAHRIYAby Mamluk

Custom Domain Not Resolving

Your custom domain doesn't load, or it resolves to the wrong place. This is nearly always a DNS record that doesn't match the DNS mode you chose, or a change that hasn't propagated yet.

Updated 3 Aug 20262 min read

Your custom domain doesn't load, or it resolves to the wrong place. This is nearly always a DNS record that doesn't match the DNS mode you chose, or a change that hasn't propagated yet.

Symptoms

  • Visiting your custom domain returns a browser error or doesn't resolve at all.
  • The domain resolves to an old or unrelated address.
  • The default hostname works, but the custom domain doesn't.

Likely causes

  • The record type is wrong for your DNS mode. Round-robin and geo modes need a CNAME; none mode needs A records pointing to each region's gateway IP.
  • The CNAME target or A record value is incorrect. The exact target is shown in your container's networking settings.
  • DNS hasn't propagated yet. Changes usually take effect within minutes but can take up to 48 hours depending on your provider and TTL.
  • A CNAME was created on a root (apex) domain. Most providers don't allow a CNAME on the apex.
  • A CDN or proxy is sitting in front of the domain and changing how it resolves.

How to fix

  1. Match the record to your DNS mode. Create a CNAME to the target shown in the console for round-robin or geo mode. For none mode, create A records pointing to each region's gateway IP. See Setting Up a Custom Domain and DNS Modes.
  2. Copy the exact target from the container's networking settings — don't guess it. A trailing character or wrong zone will stop it resolving.
  3. Check propagation with dig <your-domain> or an online DNS checker, and confirm the answer matches the target you set.
  4. For a root domain, use a subdomain (app.example.com) instead, or a provider that supports CNAME flattening or ALIAS records. To also serve www, enable WWW redirect on the apex entry.
  5. Wait for propagation. Most changes take effect within minutes; allow up to 48 hours in the worst case before assuming something is wrong.
Tip

If DNS resolves correctly but you get a certificate warning, that's a separate, later step — see TLS and Certificate Errors.