This article explains domain names, DNS concepts, and domain management tasks in Pulse Commerce.
What is DNS?
DNS (Domain Name System) is like a phone book for the internet. It translates your domain name (www.yourstore.com) into an IP address (like 192.0.2.1) that computers use to find your website. This happens automatically in milliseconds every time someone visits your site.
Key DNS Components
Name Servers
- The "master directory" that controls your domain
- Example: ns1.pulsecommerce.com, ns2.pulsecommerce.com
- Managed by your hosting provider or domain registrar
DNS Records
- Individual instructions that control how your domain works
- A Record: Points your domain to a server (e.g., yoursite.com โ 192.0.2.1)
- CNAME Record: Creates an alias (e.g., www.yoursite.com โ yoursite.com)
- MX Record: Routes email to mail servers
- TXT Record: Verification and authentication data
DNS Propagation - Why Changes Take Time
When you change DNS settings, the updates must spread across internet servers worldwide. This is called "propagation."
What to Expect:
- Timeline: 24-48 hours for changes to fully spread
- During this time: Some visitors see the old version, some see the new version (this is normal)
- Can't be rushed: Propagation depends on servers worldwide updating their cached information
Checking If DNS Changes Have Spread:
Search online for "DNS propagation checker" to see if your changes have reached servers around the world.
What is Primary URL?
The main domain name configured in your Pulse Commerce system. Used for:
- Storefront URL (if using Pulse storefront)
- Admin panel access
- Content delivery network (CDN) configuration
- Application load balancers
- Web application firewall (WAF)
- SSL certificates
- Session management
- API endpoints
How to Change Primary URL:
1Contact your Account Manager
2Request Change of Primary URL Service
3Provide new domain name
4Pulse team configures all backend systems (CDN, load balancers, WAF, SSL)
5Update DNS records as directed
6Wait for DNS propagation
7Pulse activates new Primary URL
Important: Do not attempt to change Primary URL yourself. Professional service required for proper configuration.
Timeline: Typically 5-7 business days for complete Primary URL change
Use Case: Redirect additional domain names to your primary storefront
Example: Redirect www.alternate-domain.com โ www.primary-domain.com
Benefits:
- Consolidates traffic to primary domain
- Preserves SEO value (301 is permanent redirect)
- Handles multiple brand domains
- Captures traffic from old domain names
How to Set Up:
1Contact Pulse Commerce
2Order Canonical 301 Redirect service
3Provide alternate domain names to redirect
4Update name servers or add CNAME records as directed
5Pulse configures permanent redirects
6Test redirects after DNS propagation
Common Scenarios:
- Redirect non-www to www (or vice versa)
- Redirect old brand name to new brand
- Consolidate multiple domain names
- Redirect misspellings of your domain
You can register and manage your domain name with any registrar.
Popular Registrars:
- GoDaddy
- Namecheap
- Google Domains (now Squarespace Domains)
- Network Solutions
- Hover
- Domain.com
What You Control:
- Domain registration and renewal
- Name server configuration
- DNS record management (if not using Pulse name servers)
- Domain privacy/WHOIS protection
- Domain locking and security
Integration with Pulse Commerce:
- If using Pulse storefront: Update name servers to Pulse-provided name servers
- If backend-only: Add specific DNS records provided by Pulse (name servers remain with your registrar)
If your domain is managed by Pulse Commerce Domain Name Management Service and you want to manage it yourself, follow this process:
Step 1: Send Email Request
To: billing@pulse-commerce.com
Subject Line:
<PrimaryURL>: Domain Name Management Service Release
Email Body Template:
Dear Pulse Commerce Billing,
By submitting this request for Domain Name Management Service Release, I understand and agree to the following:
- I accept sole responsibility for renewing and maintaining my domain name and acknowledge Pulse Commerce will no longer assist with this.
- I understand my Pulse Commerce service will continue to be available to me and that this request is only to release the domains listed below from Pulse Commerce Domain Name Management Service.
- I certify that as an Authorized Contact, I have the authorization to request this change of service.
Please process this request for Domain Name Management Service Release for the following domain names:
- <domain_name1>
- <domain_name2>
- <domain_name3>
Thank you,
<Authorized_Contact>
Step 2: Processing Timeline
1Billing creates work order
2Work order forwarded to Support team
3Domain transferred to end-user account at registrar
4Access details emailed to Authorized Contacts
5Timeline: Complete within 5 business days
After Transfer:
- You will receive login credentials for managing your domain
- Your Pulse Commerce service continues without interruption
- You are responsible for domain renewal
- Name servers typically remain pointed to Pulse (if using storefront)
What is a Sandbox Account?
A fully functional private site for testing functionality, settings, and alternate designs before deploying to production.
Benefits:
- Test design changes safely without affecting live site
- Try new configurations and feature changes
- Exact duplicate of production site setup
- Test multiple header designs simultaneously (Category Display Format 4)
- Train staff on new features
- Lower cost than production accounts
- Isolated environment - no impact on customers
Example URL: http://staging.domainname.com or http://sandbox.domainname.com
Use Cases:
- Testing major design overhauls
- Previewing seasonal campaigns before launch
- Training new team members
- Testing integrations with third-party services
- Quality assurance before production deployment
Setup Process:
1Contact your Account Manager
2Request sandbox account and pricing
3Pulse creates exact duplicate of production site
4Receive sandbox URL and credentials
5Test and develop in isolated environment
6Deploy changes to production when ready
Site Not Loading After DNS Changes
Causes & Solutions:
- Still propagating: Wait full 24-48 hours
- Wrong name servers: Verify name servers match Pulse-provided values
- Typo in name servers: Double-check spelling and capitalization
- Cache issue: Clear browser cache, try different device/network
- Primary URL mismatch: Contact Pulse to verify Primary URL configuration
SSL Certificate Errors
Causes & Solutions:
- Domain recently changed: SSL takes 24-48 hours to provision after DNS change
- WWW vs non-WWW mismatch: Ensure Primary URL matches your traffic pattern
- Mixed content: Check that all resources load via HTTPS
- Certificate not provisioned: Contact Pulse support
Some Users Can't Access Site While Others Can
Causes & Solutions:
- Partial propagation: Normal during DNS changes, resolves within 48 hours
- ISP DNS caching: Some ISPs cache DNS longer than TTL specifies
- Local DNS cache: Users should flush DNS cache or wait
Admin Panel Not Accessible
Causes & Solutions:
- Wrong URL: Verify correct admin panel URL from Pulse
- DNS not updated: Update name servers or add required DNS records
- Primary URL mismatch: Contact support to verify configuration
ย
Related Articles: