Domain forwarding is the process of directing traffic from one domain name to another address or server. It's used when moving your site to a new server, redirecting old domains to new ones, or connecting a custom domain to your e-commerce platform. In this guide, we explain domain forwarding types, DNS record types, and how to do it step by step.
What is Domain Forwarding?
Domain forwarding is the process of pointing a domain name (e.g., mystore.com) to a specific server IP address, another domain name, or a specific URL. Forwarding is done through DNS (Domain Name System) records.
DNS is like the internet's phone book: when a user types "mystore.com" in the browser, the DNS system translates this domain to the correct server's IP address and displays the website.
DNS Record Types
To set up domain forwarding, you need to understand the DNS record types:
| Record Type | Purpose | Example Value | Use Case |
|---|---|---|---|
| A Record | Points domain to an IPv4 address | 185.230.63.171 | Connecting main domain to server |
| AAAA Record | Points domain to an IPv6 address | 2606:4700::6810:84e5 | IPv6-enabled servers |
| CNAME Record | Points domain to another domain name | shops.beekod.com | Subdomain forwarding |
| MX Record | Specifies the mail server | mail.google.com | Email routing |
| TXT Record | Stores text-based information | v=spf1 include:_spf.google.com | SPF, DKIM, domain verification |
| NS Record | Specifies the name servers | ns1.cloudflare.com | Delegating DNS management |
| SRV Record | Specifies the address for specific services | _sip._tcp.example.com | VoIP, game servers |
Types of Domain Forwarding
1. DNS Forwarding (A Record / CNAME)
The most fundamental type. Points your domain directly to a server IP address (A record) or another domain (CNAME). The URL in the browser doesn't change; the user sees content from the target server directly.
2. URL Forwarding (301 / 302 Redirect)
Redirects from one URL to another at the browser level. The URL changes in the user's browser.
| Redirect Code | Type | SEO Impact | When to Use |
|---|---|---|---|
| 301 | Permanent Redirect | Transfers ~90-99% of link equity | Domain changes, permanently moved pages |
| 302 | Temporary Redirect | Does not transfer link equity | Maintenance mode, temporary campaign pages |
| 307 | Temporary Redirect (HTTP/1.1) | Same as 302, preserves HTTP method | API redirects, POST requests |
| 308 | Permanent Redirect (HTTP/1.1) | Same as 301, preserves HTTP method | APIs, RESTful services |
3. Frame (Masking) Forwarding
Shows the original domain in the URL bar while loading another site in the background. Harmful for SEO and not recommended by Google. Avoid using it if possible.
Point Your Domain to Beekod
Set up DNS, SSL activates automatically. Your professional e-commerce site ready in minutes.
Get Started →A Record Domain Forwarding (Step by Step)
An A record points your domain directly to a server IP address. It's the most common method for connecting your e-commerce site or web server to your domain.
Steps
- Access your DNS management panel — Go to the DNS section in your domain registrar's (Cloudflare, Namecheap, GoDaddy, etc.) control panel
- Add a new A record
- Host / Name: @ (for root domain) or www
- Type: A
- Value: Your server's IP address (e.g., 185.230.63.171)
- TTL: 3600 (or Auto) - Add an A record for www as well — So both mystore.com and www.mystore.com work
- Wait for propagation — DNS changes typically propagate within 1-48 hours worldwide
Adding A Record by Registrar
| Registrar | DNS Management Path | Host Field | Notes |
|---|---|---|---|
| Cloudflare | DNS → Records → Add Record | @ or www | Check proxy status (orange/gray cloud) |
| Namecheap | Domain List → Manage → Advanced DNS | @ or www | Namecheap DNS must be active |
| GoDaddy | My Products → DNS → Manage Zones | @ or www | Don't forget to delete old records |
| Google Domains | DNS → Custom Records | @ or www | DNSSEC managed automatically |
| Porkbun | Domain Management → DNS Records | @ or www | Clean, simple interface |
CNAME Subdomain Forwarding
A CNAME record points a subdomain to another domain name. It's frequently used when connecting a custom domain to e-commerce platforms.
Steps
- Add a new CNAME record in your DNS management panel
- Host / Name: www or shop (subdomain name)
- Type: CNAME
- Value: Target address (e.g., shops.beekod.com)
- TTL: 3600 - Verify the domain in your e-commerce platform — In platforms like Beekod, add your domain from the admin panel
- Wait for SSL activation — Automatic SSL (Let's Encrypt) typically activates within a few minutes
Important: CNAME records should not be used for the root domain (@). Use an A record for the root domain. CNAME is only suitable for subdomains (www, shop, blog, etc.).
Connect Your Domain to Beekod Easily
Add an A record or CNAME to point your domain to your Beekod store. Automatic SSL included.
How to Set Up 301 Redirects
Use a 301 redirect to permanently forward your old domain to your new address. This method is critical for transferring SEO value.
301 Redirect with .htaccess (Apache)
Add the following lines to your .htaccess file on your web server:
# Redirect old domain to new domain
RewriteEngine On
RewriteCond %{HTTP_HOST} ^olddomain\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.olddomain\.com$
RewriteRule ^(.*)$ https://newdomain.com/$1 [R=301,L]
301 Redirect with Nginx
server {
listen 80;
server_name olddomain.com www.olddomain.com;
return 301 https://newdomain.com$request_uri;
}
301 Redirect with Cloudflare (No Code)
- Go to Rules → Page Rules in Cloudflare dashboard
- URL match: olddomain.com/*
- Setting: Forwarding URL → 301 Permanent Redirect
- Destination URL: https://newdomain.com/$1
www vs non-www Redirect
For SEO purposes, you should keep only one version of your domain (www or non-www) active. Otherwise, the same content is published on two different URLs (duplicate content).
| Method | Source | Target | How? |
|---|---|---|---|
| Prefer non-www | www.mystore.com | mystore.com | www CNAME → @ + 301 redirect |
| Prefer www | mystore.com | www.mystore.com | @ A record + 301 redirect to www |
Recommendation: In modern e-commerce, non-www (bare domain) usage is more common and looks cleaner. Whichever version you choose, don't forget to 301 redirect the other.
Email MX Record Setup
When forwarding domains, be careful not to break your email service. MX records are required for custom email addresses like info@mystore.com to work.
| Email Provider | MX Record Value | Priority |
|---|---|---|
| Google Workspace | aspmx.l.google.com | 1 |
| Google Workspace | alt1.aspmx.l.google.com | 5 |
| Microsoft 365 | *.mail.protection.outlook.com | 0 |
| Zoho Mail | mx.zoho.com | 10 |
| Fastmail | in1-smtp.messagingengine.com | 10 |
DNS Propagation Time
DNS changes don't take effect immediately. It takes time for DNS servers worldwide to update.
| Record Type | Average Propagation Time | Speed Up Tip |
|---|---|---|
| A / AAAA Record | 1-24 hours | Keep TTL value low (300-600) |
| CNAME Record | 1-24 hours | Lower TTL before making changes |
| MX Record | 1-48 hours | Keep old and new MX records during transition |
| NS Record | 24-48 hours | Longest propagation time, be patient |
| TXT Record | 1-24 hours | Wait for propagation before verification |
Check Tool: You can monitor DNS propagation status in real-time at whatsmydns.net or dnschecker.org.
Launch Your E-Commerce Site with Your Own Domain
Domain forwarding, SSL, and professional email support to strengthen your brand.
Request Free Demo →Conclusion
Domain forwarding is one of the fundamental skills for managing your website. Use A records to connect to your server, CNAME for subdomain forwarding, and 301 redirects to preserve SEO value from old URLs. Always back up your existing records before DNS changes and ensure your email service (MX records) isn't affected.


