1. Website is not loading?

At is.edu we use CNAME to point our subdomains to your domain/subdomains.

A CNAME record allows a domain name to be used as an alias for another canonical (true) domain. A simple example of this could be if you have  example.com and you want us to set testing.is.edu as its alias. This means that when someone visits testing.is.edu they would be given the same content as example.com. One way to make this possible is to add a CNAME record that points testing.is.edu to example.com.

Using the query $ dig testing.is.edu we would see:

testing.is.edu       IN   CNAME  example.com
example.com          IN   A      93.184.216.34

But when you load http://testing.is.edu it wont load the example.com and you are receiving a 404 not found error. In fact that particular server (93.184.216.34) handles at least example.com, example.net, example.org and example.edu on the same IP address.
In Apache, you can host many websites using just one single IP address. This is called virtual hosting. It’s how subdomains can be created, even standalone domains. This is done by setting up an Apache configuration file containing VirtualHost directives for each domain/subdomain.

An example HTTP server that has two virtual hosts, example.com and example.net can look like this (IP address definition):

<VirtualHost 93.184.216.34:80>
  ServerName example.com
  ServerAlias www.example.com
  DocumentRoot /var/www/example.com
</VirtualHost>

<VirtualHost 93.184.216.34:80>
  ServerName example.net
  ServerAlias www.example.net
  DocumentRoot /var/www/example.net
</VirtualHost>

Two virtual host records are created internally in memory and used by Apache to compare against when a URI request arrives.

When a user types in the testing.is.edu or the IP address via a user agent, the first virtual host listed in the configuration file is used as the primary domain (i.e. in this case a 404 page).

How to fix it?

You need a dedicated IP address for your website, You should change the IP from shared to dedicated on your webhosting.

2. Cloudflare Error 1014: CNAME Cross-User Banned

We are using Cloudflare DNS management. If you are using cloudflare DNS as well you will receive “Error 1014: CNAME Cross-User Banned” error.

According to cloudflare on this article

Common cause

By default, Cloudflare prohibits a DNS CNAME record between domains in different Cloudflare accounts. CNAME records are permitted within a domain (www.example.com CNAME to api.example.com) and across zones within the same user account (www.example.com CNAME to www.example.net).

Resolution

To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must contact Cloudflare Support and specify the domains allowed to CNAME to their target domain.  A Cloudflare Pro, Business, or Enterprise plan is required on the target domain for Cloudflare Support to change default CNAME restrictions.

How to fix it?

You need a Cloudflare Pro, Business, or Enterprise plan to contact Cloudflare support to remove the CNAME restriction on your account.