Assigning a Custom Domain Name to Your Site
Custom domain assignment allows you to use your organization's domain name (e.g., portal.yourcompany.com) instead of the default Magentrix cloud domain. This process requires collaborative coordination between your organization, your IT department, and Magentrix support to ensure proper DNS configuration and SSL certificate management.
Important Collaborative Process Notice
This is a multi-party technical process that requires:
- Your Organization: Domain ownership and business requirements
- Your IT Department: DNS management and security policy compliance
- Magentrix Support: Platform configuration and SSL certificate management
Critical Recommendation: If you are unfamiliar with DNS settings management, this document MUST be reviewed with your company's IT department before proceeding. Incorrect DNS configuration can result in site downtime or accessibility issues.
Prerequisites and Requirements
Technical Requirements
- Domain Ownership: You must own and control the domain you want to use
- DNS Management Access: Ability to create CNAME records in your domain's DNS settings
- IT Department Coordination: Technical review and implementation support
Security Requirements
- No Proxy/Caching: Custom domain must not be behind proxy services or caching systems
- Direct DNS Resolution: Domain should resolve directly to Magentrix servers
- SSL Certificate Planning: Choose between Magentrix-managed or self-provided certificates
DNS Configuration Process
CNAME Record Setup
DNS Configuration Requirements:
- Create a CNAME entry in your domain's DNS settings
- Point your custom domain to:
<yourinstancename>.magentrixcloud.com - Example: If your instance is "acmetech" and you want "portal.acmetech.com":
- Record Type: CNAME
- Name/Host: portal
- Value/Target: acmetech.magentrixcloud.com
Critical Security Warning: Proxy and Caching Restrictions
Security Risk: It is strongly recommended that the custom domain NOT be behind a proxy and/or any caching features.
Security Concern: If caching is enabled, proxy servers may retrieve and serve cached information from other user sessions, potentially exposing sensitive data from one user to another.
If Proxy Must Be Used: You must ensure ALL caching configurations are completely disabled to prevent data exposure between user sessions.
DNS Propagation Timeline
- DNS Changes: Typically take up to 24 hours to propagate globally
- Testing: Use DNS lookup tools to verify CNAME record propagation
- Patience Required: Allow full propagation time before troubleshooting connectivity issues
Magentrix Support Coordination
Main Site Custom Domain Setup
Required Support Coordination for Main Sites:
- Complete DNS CNAME record creation
- Send email to support@magentrix.com with the following information:
- Request: Associate main site with custom domain name
- Domain Name: Include the fully qualified domain name (e.g., portal.acmetech.com)
- Instance Information: Your Magentrix instance name
- Wait for Confirmation: Magentrix support will configure the platform to recognize your custom domain
Custom Hub Domain Setup
Simplified Process for Custom Hubs:
- Custom Hub custom domain configuration does not require additional email to support
- DNS CNAME setup is sufficient for Custom Hub domains
- Follow standard DNS configuration process outlined above
SSL Certificate Management Options
Option 1: Magentrix-Managed SSL (Recommended)
Advantages:
- No Cost: SSL certificate management provided at no additional cost
- Automatic Management: Magentrix handles all SSL certificate lifecycle management
- Auto-Renewal: Certificates automatically renew using Let's Encrypt
- No Future Action Required: Completely hands-off SSL management
- Easier Management: Preferred option for most organizations
Process:
- Complete custom domain DNS setup
- Request Magentrix-managed SSL in your support email
- Magentrix configures Let's Encrypt SSL certificate automatically
Option 2: Self-Provided SSL Certificate
When to Use:
- Organizational security policies require specific certificate authorities
- Compliance requirements prevent use of Let's Encrypt certificates
- Existing certificate management processes must be maintained
Certificate Submission Options:
Option A: Provide Complete Certificate
- Send .pfx file containing your certificate to support@magentrix.com
- Most efficient option if you have existing certificate in .pfx format
Option B: Certificate Signing Request (CSR) Process If you cannot provide a .pfx file:
Email support@magentrix.com with Certificate Information:
- Common Name or Fully Qualified Domain Name (e.g., portal.acmetech.com)
- Organization Name
- Organizational Unit (department/division)
- City
- State/Province
- Country
Magentrix Generates CSR:
- Magentrix creates Certificate Signing Request (CSR)
- CSR sent to you via email
Submit to Certificate Authority:
- Submit CSR to your trusted third-party Certificate Authority
- Certificate Authority verifies your organization's information
- Format Preference: Choose IIS format if given certificate format options
- IIS Version: Current Magentrix IIS version is 10.0 (as of May 2023)
Certificate Installation:
- Send completed certificate files to support@magentrix.com
- Magentrix support installs certificate on your portal
Implementation Best Practices
Planning and Coordination
Pre-Implementation Checklist:
- IT Department Review: Ensure IT department reviews and approves DNS changes
- DNS Access Verification: Confirm ability to create CNAME records
- Proxy/Caching Audit: Verify no caching systems will interfere with custom domain
- SSL Strategy Decision: Choose between Magentrix-managed or self-provided certificates
- Timeline Planning: Allow 24-48 hours for complete DNS propagation and configuration
Communication Strategy
Internal Coordination:
- IT Department Briefing: Share this documentation with IT staff responsible for DNS management
- Timeline Communication: Inform users about potential brief accessibility changes during transition
- Testing Plan: Establish testing procedures to verify custom domain functionality
- Rollback Plan: Ensure ability to revert DNS changes if issues occur
Risk Mitigation
Technical Safeguards:
- DNS Backup: Document current DNS settings before making changes
- Gradual Testing: Test custom domain functionality before announcing to all users
- Monitor Accessibility: Check portal accessibility from multiple locations and networks
- Support Communication: Maintain open communication with Magentrix support throughout process
Troubleshooting and Support
Common Issues and Solutions
DNS Propagation Delays
- Allow full 24-hour propagation period before troubleshooting
- Use multiple DNS lookup tools to verify propagation across different regions
- Check CNAME record syntax and target accuracy
SSL Certificate Issues
- Verify certificate matches exact domain name (including subdomain if applicable)
- Ensure certificate format compatibility (IIS format preferred)
- Check certificate validity dates and chain completeness
Proxy/Caching Problems
- Verify no CDN or caching services are active on the custom domain
- Disable all proxy caching features to prevent session data exposure
- Test direct DNS resolution without proxy intervention
Support Resources
Magentrix Support Contact:
- Email: support@magentrix.com
- Required Information: Always include your fully qualified domain name and instance information
- Response Expectations: Allow appropriate time for DNS and SSL configuration processes
IT Department Collaboration:
- Share this documentation with your IT team before beginning implementation
- Coordinate DNS changes during appropriate maintenance windows
- Establish clear communication channels between IT, administrators, and Magentrix support
Custom domain implementation requires careful technical coordination but provides professional branding and improved user experience when properly configured through collaborative effort between all parties involved.
<< Using the Theme Builder | Configuring Currency Exchange Settings >>