If your website is not loading without the WWW prefix, your root domain (the naked domain) is missing a DNS record or a 301 redirect. To fix this, log into your DNS manager and ensure you have an 'A Record' for your root domain (@) pointing to your web host's IP address.
Naked Domain vs WWW Subdomain
These are technically two different addresses:
| | |
| Root / Naked / Apex domain | |
| | |
Root domain (naked): The bare domain without any prefix. In DNS managers, this is represented as @ or left blank.
WWW subdomain: A subdomain like any other (blog, shop, app). It just happens to be the traditional web prefix.
Here's the critical point: example.com and www.example.com are separate DNS entries. Configuring one doesn't automatically configure the other. If you only set up the WWW version, the naked domain points nowhere, hence the error.
Why It Matters: Lost Traffic
Users type URLs differently. Some include WWW, many don't. Search engines may index one version while users type the other.
Without proper configuration:
- Direct traffic gets errors
- Bookmarks break if saved without WWW
- Search engines may see two separate sites
Half your visitors hitting error pages is an emergency.
Decision Framework: A Record vs 301 Redirect
| | |
| Points naked domain directly to server IP | |
| Forwards root to WWW (or vice versa) | Cloud hosts, CDNs, SEO consolidation |
Use A Record when: Your host provides a static IP address. Both versions load independently from your server.
Use 301 Redirect when: Your host only provides a hostname (like cloud platforms), or you want to consolidate SEO authority on one canonical version.
Most modern setups use 301 redirect, pick WWW or non-WWW as your canonical, and redirect the other.
Implementation Steps
Option A: Add A Record for Root Domain
- Log into NameSilo and open Domain Manager
- Click the blue globe icon 🌎 to access DNS Manager
- For Host/Name: enter @ (or leave blank)
- For Address/Value: enter your web host's IP
- Save and wait for propagation
Option B: Set Up 301 Redirect
- In Domain Management section at your Registrar, go to Domain Forwarding
- Set root to redirect to https://www.example.com
- Choose 301 (Permanent) redirect type
NameSilo offers a "Secure WWW Redirect" DNS template, one click applies standard configuration.Â
Common Mistakes
Assuming automatic linking: Hosts don't magically connect both versions. You configured WWW; root remains unconfigured until you add its record.
Using CNAME for root: You cannot place a CNAME at the root domain, it breaks DNS. Use A Record or redirect instead.
Forgetting SSL coverage: Some certificates only cover WWW. Verify your SSL covers both example.com AND www.example.com.
Not waiting for propagation: DNS changes take time. Wait at least an hour before troubleshooting further.
What This Means for You
NameSilo's DNS Manager makes this straightforward. Add an A record for @ pointing to your host's IP, or use Domain Forwarding to redirect root to WWW. Either approach takes minutes. Both versions will work, and your traffic stops hitting error pages.
Frequently Asked Questions
Why does my site only work with www?Â
The root domain lacks an A record or redirect.
Your domain without any prefix, just example.com.
How do I redirect non-www to www?Â
Set up 301 redirect from root (@) to www in Domain Forwarding.
No difference. Consistency matters, pick one canonical version.
Do I need an A record for www?Â
Yes, or a CNAME. WWW is a subdomain needing its own record.
What do I put for the DNS host field to fix onto the root domain?Â
Enter @ or leave blank, both represent root.
Will an SSL certificate cover both www and non-www?Â
NameSilo SSL certificates cover both example.com and www.example.com. Other providers vary. How long does it take for a root domain fix to work?Â
Minutes to 1 hour depending on TTL.
.png&w=2048&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)