Why can't I access the domain name without www?

The domain name without www cannot be accessed. This is often because the domain name with www is not added to the rules when the domain name is bound. This will cause the host to not recognize the domain name with www, which will cause the domain name to be inaccessible.

The solution to the problem that the domain name without www cannot be accessed is to go to the virtual host management center and add the domain name with www in the domain name binding.

That is, both a.com and www.a.com must be bound to the host.

Why the domain name without www cannot be accessed

Let's take Western Digital as an example. Go to the domain name management center and find the domain name resolution function to see if there are two domain name resolution records, one is www and the other is @. If there is any missing, fill it in.

Why the domain name without www cannot be accessed

That is, the host names are www and @, and the corresponding types are set to CNAME. For the corresponding values, fill in the same virtual host. Some cloud service providers will provide a second-level domain name specifically for temporary testing and backup. For example, Western Digital will have a second-level domain name of xxx.gotoip*.com for each virtual host. At this time, when filling in the corresponding value, we can fill in this second-level domain name.

After completing the binding and parsing, we enter a.com and www.a.com again, and find that all of them are accessible.

At this point, the problem of why the domain name without www cannot be accessed is basically solved. However, we usually use the domain name of www as the homepage, which will result in two domain name addresses pointing to the same homepage, which will disperse the weight. If it is a Linux virtual host, you can go to the root directory. In the htaccess file, make a 301 rule, set rules for a.com and www.a.com, and specify to jump to one page. At this point, everything is solved.