Custom Domain Configuration

Metadata

• Document: CUSTOM_DOMAIN_CLIENT_SETUP
• Version: v1.1.0
• Status: ACTIVE
• Classification: CLIENT-SHAREABLE
• Owner: Customer Success + Engineering
• Approver: CTO
• Latest revision: 2026-03-11
• Next revision: 2026-06-11

1. Objective

Guide Quiker customers in custom domain configuration with a focus on DNS and redirect behavior.

2. How it works

• The Quiker canonical URL remains active as an official fallback.
• The custom domain should just redirect to the hub’s canonical URL.
• The redirect must be 301 (or 308), with preservation of path and query string.
• The destination must always be https.

Example:

• Custom domain: hub.cliente.com
• Quiker canonical URL: https://meu-hub.quiker.com.br
• Expected result: https://hub.cliente.com/ofertas?utm=abc redirects to https://meu-hub.quiker.com.br/ofertas?utm=abc

3. Information required before configuration

Ask the Quiker team:

1. Custom host that will be configured (e.g.: hub.cliente.com).
2. Canonical hub destination URL (e.g.: https://meu-hub.quiker.com.br).

Example:

• Origin: hub.cliente.com
• Destination: https://meu-hub.quiker.com.br

4. Generic step by step (any DNS provider)

1. Set the source host the client wants to use.

• Example: hub.cliente.com

2. Create the DNS record for this host in the correct zone.

• If it is a subdomain, normally use CNAME.
• If it is a root domain (cliente.com), use A/AAAA (or ALIAS/ANAME, depending on the provider).
• In case of a delegated subzone (e.g.: dev.cliente.com), confirm that the record was created in the correct delegated zone.

3. Configure a permanent redirect on the hosting/proxy/web rule provider.

• Type: 301 (or 308).
• Origin: https://<host-customizado>/*
• Destination: https://<hub-canonico-quiker>/$1
• Preserve query string: enabled.

4. Enable HTTPS on the origin domain.

• Install a valid TLS certificate for the custom host on the provider used for redirect.
• If the client does not enable HTTPS at the origin, https://host-customizado may fail.

5. Mandatory technical requirements

1. Redirect status: 301 or 308.
2. Destination must be in https.
3. Preserve path and query.
4. The hub’s canonical URL must be the one provided by Quiker.

6. Mandatory validation

Run after DNS propagation and redirect configuration:

dig +short hub.cliente.com A
dig +short hub.cliente.com CNAME
curl -I http://hub.cliente.com/
curl -I "http://hub.cliente.com/teste?utm=abc"
curl -I https://hub.cliente.com/
curl -I "https://hub.cliente.com/teste?utm=abc"

Expected result:

1. DNS resolves (dig returns IP/alias/cname).
2. curl returns 301 or 308.
3. Header Location points to the correct canonical URL.
4. path and query are preserved.
5. No loops and no incorrect chain of redirects.

7. Common errors and correction

1. Could not resolve host

• Record was created in the wrong hosted zone (e.g. main zone instead of delegated subzone).
• Wait for DNS propagation.

2. Return 302 instead of 301/308

• Adjust rule on the provider for permanent redirect.

3. https does not work on custom domain

• TLS certificate not configured on the provider that responds to the origin host.
• Redirect rule was applied only to http.

4. Redirect without path/query

• Adjust rule to preserve path and parameters.

5. Redirect to wrong hub

• Review canonical URL provided by Quiker.

8. Final checklist to send to the Quiker team

Send evidence:1. Configured custom host. 2. Canonical URL configured as destination. 3. Print of the DNS configuration (record created). 4. Print of the redirect rule configuration. 5. Output of curl -I commands (with Location visible). 6. Confirmation of 301 (or 308) with preservation of path/query.