You set up domain forwarding in GoDaddy expecting visitors to land on your intended site. Instead, you get a blank page, an error message, or the old site still showing. Traffic drops, emails bounce, and potential customers get lost. This problem can hurt your business, but it’s almost always fixable.
In this guide, you’ll learn exactly why GoDaddy forwarding fails and how to resolve it — even if you’re not a technical expert. We’ll cover step-by-step fixes, DNS insights, and real-world examples. By the end, you’ll have a clear action plan to restore forwarding and keep it working reliably.
What Is Domain Forwarding and Why Use It?
Domain forwarding (also called URL redirecting) lets you send visitors from one domain to another. For example, if you own mycompany.com and mycompany.net, you can forward the .net address to your main .com site. Anyone typing the .net version ends up at the correct page.
People use domain forwarding to:
- Protect their brand from typos and copycats.
- Simplify long or complex URLs for marketing campaigns.
- Migrate to a new domain without losing existing traffic.
- Redirect old or broken links to active pages.
GoDaddy offers two forwarding modes:
- Forward only – The browser address bar changes to show the destination URL.
- Forward with masking – The original domain stays in the address bar while the destination site’s content displays.
When either mode stops working, the cause is usually one of a handful of common issues.
Common Reasons GoDaddy Domain Forwarding Fails
Understanding why forwarding breaks helps you fix it faster. Here are the most frequent culprits:
1. DNS Propagation Delays
DNS changes don’t take effect instantly. After you adjust forwarding settings, the update can take up to 48 hours to spread across the internet. If you check within the first few hours and see the old site, this is normal.
2. Incorrect Forwarding Settings
A mistyped destination URL, wrong forwarding type, or unsaved changes will cause failure. For example, entering http://mynewsite.com instead of https://mynewsite.com can lead to security warnings.
3. Conflicting DNS Records
GoDaddy’s forwarding relies on its own nameservers. If you’ve set custom A, AAAA, or CNAME records for the root domain, those can override the forwarding rule. Even a single conflicting record can block the redirect.
4. SSL/HTTPS Mismatch
Your destination site uses HTTPS, but the forwarded domain doesn’t have a valid SSL certificate. Browsers then block the redirect or show a “Not Secure” warning. Over 90% of web traffic now uses HTTPS, so this is a growing issue.
5. Forwarding Loops
If Domain A forwards to Domain B, and Domain B forwards back to Domain A, you create an infinite loop. Browsers detect this and refuse to load the page.
6. Masked Forwarding Blocked by the Destination
Some websites explicitly block being displayed inside an iframe (the technique masking uses). You’ll see a blank page or an error instead of the content.
7. Expired or Inactive Domain
If the domain itself is not registered, expired, or suspended, forwarding will never work — no matter how perfect your settings are.
8. Browser or DNS Cache
Your computer or network may remember older DNS records. Clearing the cache or testing on a different device often reveals the true status.
9. GoDaddy System Outages or Maintenance
Even large providers experience temporary downtime. During these periods, forwarding may stop.
10. Interference with Email Hosting
Forwarding itself doesn’t affect email (MX records are separate), but changing nameservers or DNS records can accidentally remove your email settings, breaking delivery.
DNS Propagation: Why Your Changes Take Time
DNS propagation is the delay between when you save a change and when it’s visible everywhere. The internet’s directory system caches DNS records at many levels — your ISP, your router, and your browser. Each cache refreshes on its own schedule.
For GoDaddy forwarding, propagation usually completes within 24–48 hours, but it can be faster (sometimes minutes) or slower depending on the TTL (Time To Live) value of your DNS records. If you’ve just made a change, wait at least a full day before troubleshooting further.
Step-by-Step Troubleshooting Guide
Follow these steps in order. Stop when the forwarding works.
1. Wait for DNS Propagation
After making any forwarding change, allow 24–48 hours. During this time, test occasionally rather than repeatedly.
2. Verify Domain Status
- Log into your GoDaddy account.
- Go to My Products > Domains.
- Check that the domain is Active and not expired or locked.
3. Review Forwarding Settings
- Select the domain, then DNS > Forwarding.
- Click Edit next to the forwarding rule.
- Confirm:
- The destination URL is correct (including
https://if needed). - The forwarding type is what you intended (Permanent 301 or Temporary 302).
- The mode is “Forward only” or “Forward with masking”.
- The destination URL is correct (including
4. Remove Conflicting DNS Records
- In the DNS management page, look for any A, AAAA, or CNAME records pointing to an IP address or another hostname.
- If you see such records for the root domain (
@), delete them or switch back to GoDaddy’s default nameservers. This is a common oversight — just like diagnosing a household appliance issue, you need to check every component.
5. Clear Browser and DNS Cache
- Clear your browser’s cache and cookies.
- Test in private/incognito mode.
- If possible, test on a different device or network (e.g., your phone on mobile data).
6. Use a DNS Propagation Checker
Visit a site like whatsmydns.net and enter your domain. It will show whether the forwarding rule has propagated to servers worldwide. If you see mixed results, wait longer.
7. Avoid Forwarding Loops
Ensure the destination domain does not have a forwarding rule pointing back to the original domain. This is surprisingly easy to create when managing multiple domains.
8. Disable Masked Forwarding
If you’re using masking and seeing errors, switch to “Forward only”. Some hosts or platforms block iframe-based redirects. Masking also harms SEO, so it’s best avoided unless absolutely necessary.
9. Check SSL Certificate
If your destination uses HTTPS, make sure the forwarded domain has a valid SSL certificate. GoDaddy’s basic forwarding does not include free HTTPS for the forwarded domain. You may need to purchase an SSL certificate or use a third-party service like Let’s Encrypt.
10. Contact GoDaddy Support
If nothing works, reach out to GoDaddy’s support team. Provide your domain name, forwarding settings, and a description of the problem. They can check server-side logs.
How to Check Your Domain and DNS Settings
Before making changes, take a snapshot of your current DNS records. This helps you revert if something goes wrong.
- Log into GoDaddy.
- Navigate to DNS Management for your domain.
- Note all existing records (A, AAAA, CNAME, MX, TXT, NS).
- Compare them against the requirements for forwarding (GoDaddy default nameservers, no conflicting root records).
For example, if you see an A record for @ pointing to a specific IP, that can override forwarding. Remove it.
Understanding Forwarding Types: 301 vs 302
| Redirect Type | Use Case | SEO Impact |
|---|---|---|
| 301 (Permanent) | Moving to a new domain permanently | Search engines transfer ranking power to the new URL |
| 302 (Temporary) | Short-term redirects, testing | Search engines keep the old URL indexed; no SEO transfer |
Best practice: Use a 301 redirect unless you plan to undo the forwarding soon. This preserves your search engine traffic.
Masked Forwarding: When to Avoid It
Masked forwarding keeps your original domain in the browser’s address bar while showing content from the destination site. It sounds useful, but it causes several problems:
- Many websites block iframe embedding, resulting in a blank page.
- Some browsers display security warnings for mixed content.
- Search engines may see duplicate content or no content at all, hurting rankings.
- Features like contact forms, login pages, and JavaScript-dependent elements often break.
If you need masking, test the destination site in an iframe first using a tool like iframe-test.com. If it fails, switch to “Forward only”.
HTTPS Forwarding Challenges and Solutions
In 2026, most websites require HTTPS for security and browser trust. However, GoDaddy’s basic domain forwarding does not automatically provide an SSL certificate for the forwarded domain. This means visitors may see a “Not Secure” warning or a redirect that fails.
Solutions:
- Purchase an SSL certificate for the forwarded domain through GoDaddy or another provider.
- Use a third-party DNS service like Cloudflare, which offers free HTTPS redirects via their SSL/TLS settings.
- Switch to a registrar that includes free HTTPS forwarding (e.g., Google Domains or Namecheap with paid SSL).
Forwarding with Third-Party DNS (Cloudflare, etc.)
If you use Cloudflare, Amazon Route 53, or any external DNS provider, GoDaddy’s built-in forwarding will not work. The forwarding rule lives only in GoDaddy’s DNS servers.
To redirect when using third-party DNS, you must set up the redirect at that provider. For Cloudflare, create a Page Rule with a 301 redirect to your destination. For others, use their URL forwarding or redirect features.
A common mistake is setting up forwarding in GoDaddy while the domain’s nameservers point to Cloudflare. The result: nothing happens. Always check where your DNS is managed before troubleshooting.
How to Test If Forwarding Is Working
Testing correctly saves you time. Use these methods:
- Direct browser test: Type the source domain in a regular browser window. Note the final URL.
- Redirect checker: Use an online tool like httpstatus.io to see the HTTP status code and final destination.
- Private browsing: Test in incognito or private mode to bypass your browser cache.
- Different network: Use your phone’s mobile data or ask a friend in another city to test. This rules out local caching.
Preventing Future Problems
Once you’ve fixed the forwarding, take these steps to avoid a repeat:
- Stick with GoDaddy’s default nameservers unless you have a strong reason to change.
- Document all DNS records before making edits.
- Keep your domain renewal auto-pay active.
- Monitor forwarding with a free service like UptimeRobot or a simple redirect checker.
- If you switch DNS providers, migrate all records (including MX for email) carefully.
- For critical sites, set up a backup landing page (on a subdomain) that you can redirect to manually if forwarding fails.
Real-World Example: Diagnosing a Broken Forward
Imagine you own greengardenshop.com and want it to forward to greengardenstore.com. You set up forwarding in GoDaddy, but after 24 hours, visitors see “This site can’t be reached.”
Step-by-step diagnosis:
- Check domain status – both are active.
- Wait another 24 hours for propagation.
- Use a DNS checker – the forwarding rule isn’t showing.
- Log into GoDaddy DNS – you notice an A record for
@pointing to an old hosting IP. That’s overriding the forwarding. - Delete the A record. Save.
- Wait 30 minutes and test again – the redirect works.
- Confirm the destination URL uses HTTPS and the forwarded domain has a valid SSL certificate.
This scenario is common. The fix took only a few minutes after identifying the conflict.
Frequently Asked Questions
Why does my GoDaddy domain forwarding take so long to work?
DNS propagation can take up to 48 hours. Your ISP, router, and browser all cache records. Patience is usually the solution.
Can I use domain forwarding and email hosting together?
Yes, but only if you keep your MX records intact. When you change nameservers or DNS settings, make sure to copy over your email server records. If you lose them, email delivery stops.
What’s the difference between “Forward only” and “Forward with masking”?
Forward only visibly changes the URL in the address bar. Masking keeps the original domain displayed but shows the destination site’s content inside a frame. Masking often breaks site functionality and hurts SEO.
How do I set up HTTPS forwarding with GoDaddy?
GoDaddy’s basic forwarding does not include free HTTPS for the forwarded domain. You need to buy an SSL certificate for that domain, or use an external service like Let’s Encrypt that provides free SSL certificates.
My forwarding works on some devices but not others — why?
This is almost always a cache issue. Clear your browser cache, test in private mode, or use a different network. Local ISPs may also update DNS slower than others.
Conclusion
Domain forwarding not working in GoDaddy is frustrating, but the fix is almost always straightforward. The most common causes — DNS propagation delays, conflicting records, HTTPS mismatches, and masked forwarding blocks — are easy to diagnose and resolve with the steps in this guide.
Your next step: Start with the troubleshooting checklist above. Check your domain status, verify your forwarding settings, and remove any conflicting DNS records. If you suspect a DNS conflict, use a propagation checker to confirm. If you’re still stuck after 48 hours, contact GoDaddy support with your details.
By understanding the mechanics behind forwarding and applying these systematic fixes, you’ll keep your visitors flowing to the right place — no lost traffic, no broken links, and no headaches.
