Fix For Cpanel Www Not Working
When www is not working, the first thing we check is the DNS entry. In the DNS zone, we confirm that the entry for www is added correctly.
If the issue is confirmed to be with DNS, we edit the DNS Zone and make sure www is set up as a CNAME on the domain.
This can be done from WHM => DNS Functions => Edit DNS Zone option.
Edit DNS zone to add CNAME
Strict caution has to be exercised while editing DNS zones, as even a slight mistake such as a missing . can corrupt the DNS entry.
As DNS changes involve propagation delay, it can take time for it to reflect world-wide. We test and confirm the changes locally in the DNS servers and verify they are working fine.
For websites that are hosted in external DNS servers, the updates have to be done in those servers for the site to work fine.
If the DNS is fine, we check and confirm that the entries in Apache configuration file are listed properly. Any missing entries in the conf files are added.
As cPanel automatically reloads Apache configuration files, the changes to the configuration has to be done via the appropriate WHM interface. Manual edits may get lost in updates.
If the configuration file is corrupt, we rebuild it from scratch. Backups are taken before edits and Apache is restarted after the change. Caution has to be taken to avoid incorrect entries that can stop Apache functioning.
You Transferred Dns Service First But You Didn’t Wait Long Enough Before Transferring Domain Registration
When you transferred DNS service to Amazon Route 53 or another DNS service, you updated the configuration for your domain with the domain registrar to use the name servers for the new DNS service.
DNS resolvers, which respond to requests for your domain, commonly cache the names of name servers for 24 to 48 hours. If you change the DNS service for a domain and replace the name servers from one DNS service with the name servers for another DNS service, it can take up to 48 hours before DNS resolvers start using the new name servers and, therefore, the new DNS service.
Here’s how transferring your DNS service and then transferring your domain too soon after can cause your domain to become unavailable on the internet:
You transferred DNS service for your domain.
You transferred your domain to Route 53 before DNS resolvers started to use the name servers for your new DNS service.
Your previous registrar canceled DNS service for your domain as soon as the domain was transferred to Route 53.
DNS resolvers are still routing queries to your old DNS service, but there are no longer any records that tell how to route your traffic.
When caching expires for the name servers for the old DNS service, DNS will start to use your new DNS service. Unfortunately, there is no way to accelerate this process.
Dns Propagation: Why Doesnt My Domain Work
Are you seeing this when you try to reach your domain?
Did you recently change where your domain points to? Move your domain to a CMS ?
You dont need to be a DNS expert to fix it, but it helps to have some understanding of how the system works. Were going to give you a quick overview of how issues with DNS propagation can result in messages like the one above, and how you can fix most of these issues in just a few steps.
You May Like: Transfer Godaddy Domain To Wix
What You Can Do About Dns Caching
If you have time, you can just wait for the cache to expire. It helps if you know one key piece of data about the old DNS record you replaced: its TTL. TTL means time to live and it indicates to DNS resolvers how long to keep the record in its cache. In a DNS record, a TTL is measured in seconds. BUT theres a catch resolvers wont always honor the TTL. That means, even with a short TTL, it could take anywhere between 3 and 24 hours for you to see your update. If you dont have time to wait, then you can
2. Try from a different network
Since the DNS resolver you use is tied to your internet service provider, if you try your domain name from your smartphone with the WiFi turned off, you should be able to get the new DNS record
3. Query the server directly from a terminal
If you can rule out caching, though, the issue might be something else, like
Domain Expired Or Suspended
Finally, the last reason your DNS might not be working is if your domain name has expired. This would cause your domain name not to resolve at all .
Another reason is if your domain has been suspended, for example, for a legal issue.
For an expired domain name, you would see that in your dashboard. As for a suspended domain name, the only way to tell whether thats causing your DNS problem would be using the Whois. Check the Domain Status and if it says clientHold or serverHold, get in touch with your registrar to resolve the issue.
Read Also: How Much To Buy A Domain Name
Causes For Cpanel Www Not Working
It is a long-standing practice that domain names are accessed in browsers with the prefix www, which denotes the World Wide Web.
For a domain to work with www prefix, it should have entry in 2 locations in a cPanel server.
1. DNS record In the DB record for the domain, there should be a CNAME entry corresponding to www.
www IN CNAME domain.com.
This entry is added by default in the DNS record, whenever a domain is created in the WHM. But in certain scenarios, this www entry may get deleted or corrupt, causing domain to not work with www prefix.
2. Apache configuration file Another file where the entry for www is required, is the web server configuration file usually located at /etc/apache2/conf/httpd.conf.
The entry for each domain in the config file would be of the format:
< VirtualHost xx.xx.xx.xx:80> ServerName domain.comServerAlias www.domain.comDocumentRoot /home/user/public_html
The ServerAlias entry in the VirtualHost for www prefix instructs the web server to load the same content as the domain name, when accessed with www also.
This entry is also added by default into the Apache configuration file during domain creation. But cPanel provides option to override the entries in the httpd.conf file.
During Apache configuration corruption or custom setting changes made for Apache, the entries in the config file can get messed up and cause www to not work.
My Domain Name Is Not Working Properly
basically i have a website i.e www.example.com
when i enter www.example.com it deosnt workbut when i enter it works why is this happening!!
- Going to kornar.com takes me to a different site than www.kornar.com this is very strange!Dec 25, 2010 at 6:46
- put more info language,CMS,framework etcDec 25, 2010 at 6:47
- 1It’s definitely a server thing. I don’t know much about what exactly is going on, but it’s somewhere in the ball park of how different websites will use www2, www, or route traffic through both. I have no clue, though. This was just an interesting question. Good luck!Dec 25, 2010 at 6:47
- Have you newly registered this domain?
You May Like: Why Are Some Domains So Expensive
Add Your Own Domain Before Using Bitly’s Complimentary Domain
If you haven’t added a domain yet, Bitly offers a .
If you have just redeemed a complimentary domain through Bitly and you receive a verification failed status, please allow up to 24 hours for the settings to verify and attach to your account. You can also remove the domain from your account and re-add it to verify.
Is Your Domain Newly Hosted
Then the SSL certificate has probably not been activated yet. From the moment a domain is registered or transferred to One.com, it can take up to 24 hours for SSL to work. Please try again tomorrow.
Is it still not working after 24 hours? Then maybe something went wrong with the activation of your certificate. Please contact our support so we can check it for you and manually activate the certificate if needed.
Problems Resolving A Domain
If Google Public DNS has problems resolving a certain domain name,enter it on the dns.google detail page.If the problem is with a particular DNS resource record type,enter it in the “RR type” text field .Press Enter or click Resolve to see the results.
In the detailed results, there may be a line with “Comment”: at the bottomwith diagnostics about your DNS query. For example, you might see “DNSSEC validation failure. Check http://dnsviz.net/d/dnssec-failed.org/dnssec/and http://dnssec-debugger.verisignlabs.com/dnssec-failed.org for errors”
Visit all comment URLs to see detailed diagnostics that can identify the cause of resolution problems.
If there is a Comment line that matches one of the following entries,click the corresponding link to go directly to a specific diagnostic step,or just start with the first step of Domain troubleshooting.
- DNSSEC validation failure
- If you see this, disable validation by clicking the DNSSEC toggle,and click Resolve to retry the query. If that succeeds ,there is a DNSSEC problem see DNSSEC troubleshooting.Otherwise, see Name server troubleshooting.
- Name servers
If you have problems with large records ,read about troubleshoting large responses.
Services Not Working With Your Domain
We can help you track down issues with your domain’s DNS setup. The domains troubleshooter in Microsoft 365 will show you any records that need fixing, and exactly what the records need to be set to.
Got your DNS set up correctly, but mail doesn’t work in Outlook on your desktop? Check out the different mail flow scenarios you can have with Microsoft 365 to make sure you’ve got things set up correctly for your business. Or get more troubleshooting help with email here: Fix Outlook problems.
Recommended Reading: Should I Buy My Domain Through Shopify
Wait For Dns Propagation
If you just purchased or transferred a domain, note that there is a 24-48 hour propagation period that must take place before your website is live at the domain name. You must wait until the DNS propagation period is complete for the website to appear when the domain name is searched in a web browser. Learn more about transferring your domain to Square.
To help make our troubleshooting process more efficient, take these important troubleshooting steps before you contact Square Support.
How Can I Set Up An A Record For My Domain
A recordNamecheap accountDomain ListManageAdvanced DNSHost recordsAdd New RecordA RecordTypeHostroot domainwwwwww.yourdomain.tldA Record | www | 126.96.36.199A Record | blog | 188.8.131.52 – A Record | * | 184.108.40.206Save changes30 minutes same host
Don’t Miss: How Much To Purchase A Domain Name
Domain Has Been Connected To Zyro Servers Very Recently
If you connect a domain to a website for the first time , it normally takes up to 24 hours for the website to appear online.
It takes time because the information about your domain needs to be updated on all servers worldwide. Some domain registrars take longer than others. Even if you have correctly pointed the domain to Zyro servers, it may sometimes take up to 48 hours for it to synchronize all around the globe.
P.S. You can check what nameservers your domain is currently connected to in the public domain database WHOIS.Simply insert your domain there, and you should see your domain’s nameservers set to dns1.zyro.com and dns2.zyro.com like in the example below.
Another way to check the domain status is to use the DNS checkertool. Insert your domain there in the domain.com format . Select NS and click Search. If you see red crosses, your domain information is still propagating worldwide.
Can’t Verify Your Domain
There are a couple of common reasons that domain verification doesn’t work as it should:
The verification record value isn’t quite correct. Doublecheck that you’ve copied and pasted the exact value into the TXT verification record at your DNS host. One common issue is not including the “MS=” part of the record. We need that too!
The record hasn’t been saved. At some DNS hosts, you have to take an extra step to save the zone file so that it will update across the Internet. Make sure you’ve saved your changes so Microsoft 365 can see and verify the record.
The record hasn’t updated across the Internet. It typically only takes a few minutes for us to be able to see the new record, but occasionally it can take as long as a few hours.
Recommended Reading: How To Unlock Godaddy Domain For Wix
Configure The Dns Record For Your Own Custom Domain
This is the most common reason for domain verification problems. If you are adding your own domain from an external host, like GoDaddy, you will want to ensure your DNS record includes the following settings in order to point to Bitly:
For more details, see our step-by-step guide on configuring your custom domain.
Your Domain Name Is Not Working Try These Five Easy Fixes
- DriverFix has been downloaded by 0 readers this month.
The excitement of launching your very first website can be stymied by domain issues. Nothing is as frustrating as finalizing the design of your website and launching it, only to be met with a DNS_PROBE_FINISHED_NXDOMAIN error.
Fret not, because youre not alone. Being unable to load your website because your domain name is not working is a fairly common problem. One that is remediable with the following steps in this guide.
Recommended Reading: How To Find Email Domain And Server
Play The Waiting Game
If youve just registered your domain, its important to note that it may take a while for the registration to be finalized. The registrar of your choice will need a bit of time to make DNS changes. Usually, this process will take an entire day .
Sometimes it can take up to 48-hours for the domain to effectively work globally. Therefore, youll need to exercise a little patience before escalating the issue further with the host or registrar.
Did any of these steps work for you? Do you have any qualms or questions? If you do, dont hesitate to reach for the comments section below.