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.
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.
Multiple A Type Records
An A record is used to point to an IP address associated with your website. This is opposed to a CNAME record, which maps your domain name to another domain name. A quirk of this difference is that you can only have one CNAME record for particular subdomain , but you can have multiple A records.
Its possible, then, that if your DNS update involved updating an A record, you really just added a new A record and left the old one where it was.
What makes this error even harder to figure out is that sometimes your computer will get one response for an A record query, sometimes another. If the different IP addresses serve different websites, the result is that sometimes youll get one website, sometimes youll get another.
And theres yet another twist: the system of IP addresses is in the process of transitioning from version 4 to version 6 . The problem is that v4 IP addresses are too small and there are not enough of them. IPv6 addresses are much longer. The problem for DNS is that you cant have a regular A record with an IPv6 address.
For that, you need a AAAA record.
And thats what can make this problem hard to spot. If you update just the A record and not the AAAA record, your update will apparently not work either.
Don’t Miss: Do I Need Private Domain Registration
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.
Viewing Your Sites Ip Address In Your Browser
Due to the way that DreamHost configures Apacheunless you have purchased a Unique IP address for your domainattempting to view your site by entering the IP address in your browser automatically gives you the ‘Site Not Found’ error. This is because youre viewing the shared IP of your web server, not the IP of your site.
If you absolutely need to view your site through an IP address, you must purchase a Unique IP. You can read more about Unique IPs in the following article:
Don’t Miss: How Much Are Domains
Domain Does Not Work With Www
If you can access your website using your domain without www. but not with www.mysite.com altogether, most likely you need to check your DNS zone settings to see if you have an A record for www. entry of your domain.
The A record should point to the same IP as your default main domain. You can check the IP in your account’s Details section.
NOTE: For best results, it’s simply recommended to point your domain to our nameserversto avoid issues like this 🙂
Errors Related To Internet Explorer
If you are using Internet Explorer, you may see any of the following error messages:
“No verifier returned from client”
“Origin header required”
“Failed cross origin authentication”
When both the Auth0 domain and the app domain are in the same trusted or local intranet zone, Internet Explorer does not treat the request as a cross-domain request and therefore does not send the cross-origins header.
If you see any of these errors and you are using Embedded Login, you can move one of the sites out of the trusted or local intranet zone. To do this:
Go to Internet Options > Security.
Select the Local Intranet Zone tab and go to Sites > Advanced. Add your domain.
Return to the Security tab, and make sure the proper zone has been selected.
Click Custom Level and look for Access data sources across domains under the Miscellaneous section. Check the radio button next to Enable.
Alternatively, you can remove reliance on cross-origin authentication by implementing .
Read Also: How Much For A Domain Name
You Transferred Domain Registration And Specified The Wrong Name Servers In The Domain Settings
When you transfer domain registration to Amazon Route 53, one of the settings that you specify for the domain is the set of name servers that will respond to DNS queries for the domain. These name servers come from the hosted zone that has the same name as the domain. The hosted zone contains information about how you want to route traffic for the domain, such as the IP address of a web server for www.example.com.
You might have accidentally specified the name servers for the wrong hosted zone, which is especially easy if you have more than one hosted zone that has the same name as the domain. To confirm that the domain is using the name servers for the correct hosted zone and, if necessary, update the name servers for the domain, perform the following procedures.
If you specified the wrong name server records when you transferred the domain to Route 53, it can take up to two days after you correct the name servers for the domain before DNS service is fully restored. This is because DNS resolvers across the internet typically request the name servers only once every two days and cache the answer.
To get the name servers for your hosted zone
If you’re using another DNS service for the domain, use the method provided by the DNS service to get the name servers for the hosted zone. Then skip to the next procedure.
If you’re using Route 53 as the DNS service for the domain, sign in to the AWS Management Console and open the Route 53 console at .
Choose Add or Edit Name Servers.
# Inactive Netlify Dns Zone
A common DNS configuration issue is an inactive Netlify DNS zone. This prevents our service from creating or updating the automatic Lets Encrypt SSL certificates for your custom domain. This can cause problems for branch subdomains. For more information, visit our Forums for a verified Support Guide on how to detect and fix inactive Netlify DNS zones.
Don’t Miss: Find Mail Server For Domain
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.
# Certificates And Https
There are many reasons why adding a Netlify certificate or uploading a custom certificate might not work. The common causes are listed below, but if they dont seem to apply to you or you have additional questions, our Support team will be happy to help out!
Most importantly, youll need to configure the DNS for the custom domain before Netlify can issue a certificate for you. Netlify must validate the domain in order to provision the certificate, and this step cannot be completed until the DNS records for your custom domain are pointing to our servers.
All previous DNS settings must have their cache timeouts expired. The TTL setting on a DNS record determines how long the record may be cached. This cache must expire before your new DNS settings can be validated for certificate provisioning.
If your site is configured to go through another service , you need to disable that routing before we can provision the certificate. Netlify must handle TLS termination to be able to provision a certificate.
It is possible that the name servers we use have some old cached values for your domain name. You can attempt to accelerate cache expiration for your domains using the Flush Cache tool provided by Google Public DNS.
It is possible that we will get a certificate for one name and not for another . In this case selecting Renew certificate should resolve the issue. If it doesnt, please post in the Netlify Support Forums so our support engineers can repair the certificate.
Also Check: How Much Does It Cost To Register A Domain Name
Clear Your Browsers Cache
These steps should work for all Chromium-based browsers. You can follow a similar process to clear the cache on all other browsers as well. If youre still unsure, we recommend reading through your browsers support pages.
This solution works particularly well for users who have migrated their website to a new hosting service or changed the IP address. If the websites IP address does not match the domain in your browsers cache, it may cause some problems.
This is because your browser will try to consult its cache instead of the authoritative name server.
Clearing your browsers history may take a while. Youll need to ensure that all active tabs are closed if you want it to work effectively. If you find that its taking too long, you might have to restart your browser and go through the above steps again.
Why Isnt Your Domain Name Working
DNS is a naming system that converts alphanumeric domain names into numeric IP addresses. Essentially, DNS servers act as translators. When you enter a web address in your browser, the router sends it to the DNS server, where it is resolved and returned as an IP address.
However, if the DNS server cant handle this name resolution process correctly, the end result is usually a message that the DNS server is not responding. A non-responsive DNS server means that your browser has failed to connect to the Internet.
DNS errors are usually caused by problems on the user side, whether it is the network or Internet connection, improperly configured DNS settings or an outdated browser. They can also be caused by a temporary server failure that makes DNS unavailable.
Thus, you can solve the problem simply by changing your browser. In other cases, you may need to disable connections, change DNS servers, or clear the DNS cache.
Also Check: How To Unlock Godaddy Domain For Wix
The Root Cause Of ‘site Not Found’
The ‘Site Not Found’ error means the IP address your domain is using is not pointed to the correct IP.
More technically, the ‘Site Not Found’ error means that the DNS records for your domain are resolving to the IP address of an Apache web server service that is not configured for your domain.
When this happens, the Apache web server is designed to only show the first domain listed in its config file. To make sure that nobody’s site ever accidentally shows a random site hosted on the same Apache service, DreamHost makes the first domain in all its config files show the same custom error page.
There are a few reasons why your IP may not be correctly pointed to your web server IP which are explained below.
Check If The A Records Are Correct
Check if the A record is configured properly or not. Normally this setting is automatically configured by the Control panel. In case anyone has updated some manual entry in the A record of the website, then this section needs to be verified.
There is one more scenario i.e. if you are using different nameservers and dont want to change the nameservers. In this case, your A records should be proper and need to point towards the A records of hosting provider.
Also Check: Domainnamechecker
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