Shopping Portal

CNAME Implementation Guide

9min

Overview

This guide outlines the steps required for partners to configure a CNAME record to point their desired subdomain or custom domain to the hosted shopping portal. By completing these steps, the partner ensures their users can access the shopping portal under their own domain while the actual hosting is managed by Wildfire.

Prerequisites

  • Access to the DNS management system for the partner's domain (e.g., Cloudflare, GoDaddy, AWS Route 53, etc.).
  • The CNAME target provided by Wildfire
  • Confirmation from Wildfire that the hosted shopping portal is ready to be linked.

Step-by-Step Instructions

1. Choose a Subdomain or Custom Domain

The partner should decide where they want to host the shopping portal. Examples:

  • shop.yourwebsite.com (Subdomain)
  • yourwebsiteshopping.com (Custom Domain, requires additional steps)

2. Configure the CNAME Record

  1. Log in to your DNS provider's management portal.
  2. Navigate to the DNS settings or domain management section.
  3. Add a new CNAME record with the following details:
    • Type: CNAME
    • Name (Host): shop (if using shop.yourwebsite.com) or @ (if using a custom domain)
    • Value (Target): [CNAME target provided by Wildfire]
    • TTL: Default or 3600 seconds (1 hour)
  4. Save the record and allow time for DNS propagation (may take up to 24 hours).

3. SSL and Security Considerations

Wildfire will provide SSL/TLS certificates to ensure secure browsing. However, if a custom domain (not a subdomain) is used, additional SSL configuration may be required.

4. Verify the Configuration

  • Use a DNS lookup tool (e.g., dig shop.yourwebsite.com or an online DNS checker) to confirm that the CNAME record points to the correct target.
  • Inform Wildfire once the CNAME is set up so they can complete the configuration on their end.

5. Testing and Go-Live

  • Once Wildfire confirms the setup, test the URL to ensure it correctly loads the shopping portal.
  • Perform final checks for functionality, security, and branding.

Troubleshooting

  • CNAME not resolving: Wait for DNS propagation, clear local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS), and retry.
  • Incorrect redirection: Verify the CNAME record value and ensure there are no conflicting A or CNAME records.
  • SSL certificate issues: Contact Wildfire if an SSL error appears.

Support

For further assistance, reach out to Wildfire support team at [email protected].

Updated 11 Mar 2025
Doc contributor
Did this page help you?
PREVIOUS
Shopping Portal Authentication
NEXT
Commission History
Docs powered by Archbee